The Calcilte-based engine will be released gradually in 2.x releases. As
far as I know, we don't need for Ignite 3.0.
-
Denis
On Tue, Sep 15, 2020 at 7:43 PM 18624049226 <18624049...@163.com> wrote:
> It seems that the new Calcite based SQL Engine is not included in the
> plan, and this
It seems that the new Calcite based SQL Engine is not included in the
plan, and this proposal is abandoned?
在 2020/9/16 上午5:24, Kseniya Romanova 写道:
Hi, igniters!
Thanks to all who attended today's event, that was a really warm community
gathering even though we met online! And thanks to Val
For what it is worth, we use messaging in Ignite to provide grid
notifications for various purposes. These might stimulate compute
operations in the message recipients, but they don't represent compute.
If messaging is removed, how would Ignite provide the ability for a node to
listen to events
Hi Devin,
What are the exact configuration changes that force you to restart the
cluster? What is your process of onboarding a tenant?
The reason I'm asking is that adding new caches should not require a
cluster restart, even in the current version, but it's possible that you're
hitting one of
Hi, igniters!
Thanks to all who attended today's event, that was a really warm community
gathering even though we met online! And thanks to Val for his
presentation. I hope these materials will help to run the discussion about
Ignite 3.0[1]
Video: https://youtu.be/zPuLJgUfLaM
Slides with all
Hi Igniters,
I've detected some new issue on TeamCity to be handled. You are more than
welcomed to help.
*New Critical Failure in master MVCC Cache 7
https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_MvccCache7?branch=%3Cdefault%3E
No changes in the build
-
Hi Igniters,
I've detected some new issue on TeamCity to be handled. You are more than
welcomed to help.
*Test with high flaky rate in master
ZookeeperDiscoveryMiscTest.testClientNodesStatus
Hi Everyone,
I'd like to start a discussion on how to eliminate the need to restart the
entire cluster whenever configuration changes need to be made to caches.
The need to deactivate and restart the entire cluster every time config
changes must be made has caused problems with our ability to
I understand now, thanks Pavel, initial discussion didn`t touch kuber theme ...
>Вторник, 15 сентября 2020, 18:22 +03:00 от Pavel Tupitsyn
>:
>
>Zhenya, sure, let me explain.
>
>Health checks are a common practice in modern deployments, quote [1]:
>"Health probes can be used by container
Hello,
I have finished the last checkpoint refactoring
ticket(https://issues.apache.org/jira/browse/IGNITE-13207).
In general, there are several new classes were created(it mostly extracted from
GridDatabaseSharedManager). More detailed description you can find on the
ticket.
If somebody
Hello,
This idea looks great in my opinion. I agree that a more common approach would
be better but I am the same as Kirill haven't found the better one. So in my
point of view, this library is better than nothing, and if nobody will
recommend a different one we can take picocli right now.
--
Zhenya, sure, let me explain.
Health checks are a common practice in modern deployments, quote [1]:
"Health probes can be used by container orchestrators and load balancers to
check an app's status.
For example, a container orchestrator may respond to a failing health check
by halting a rolling
Hello, Alex.
We can’t restrict dot in the cache name because it will break backward
compatibility of Ignite.
> 15 сент. 2020 г., в 16:38, Alex Kozhenkov написал(а):
>
> Yeah, that would be even better for all cases.
>
> вт, 15 сент. 2020 г. в 15:51, Ilya Kasnacheev :
>
>> Hello!
>>
>> This
Yeah, that would be even better for all cases.
вт, 15 сент. 2020 г. в 15:51, Ilya Kasnacheev :
> Hello!
>
> This seems suspiciously similar to
> https://issues.apache.org/jira/browse/IGNITE-7264
>
> Maybe we need to restrict cache names after all.
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> вт, 15
Pavel, i read whole thread, show me the reason why this functionality need to
be external ?
>
>
>Health checks are the primary use case. See linked user list thread.
>
>On Tue, Sep 15, 2020 at 12:26 PM Zhenya Stanilovsky
>< arzamas...@mail.ru.invalid > wrote:
>
>>
>> Whats the usage of such
> Whats the usage of such API
Health checks are the primary use case. See linked user list thread.
On Tue, Sep 15, 2020 at 12:26 PM Zhenya Stanilovsky
wrote:
>
> Whats the usage of such API ? Igor can you clarify please ?
>
> >Personally I believe that public API still can be helpful, as it
Hello!
This seems suspiciously similar to
https://issues.apache.org/jira/browse/IGNITE-7264
Maybe we need to restrict cache names after all.
Regards,
--
Ilya Kasnacheev
вт, 15 сент. 2020 г. в 13:49, Alex Kozhenkov :
> Hi, guys!
>
> Cache names may contain dots, but in metic names we create
Hi, guys!
Cache names may contain dots, but in metic names we create hierarchy with
dots.
So with the cache name "Person.statistic" we will have a metric
"io.statistics.sortedIndexes.SQL_PUBLIC_Person.statistic._key_PK" which is
not obvious what is a cache name and what is next hierarchical
Whats the usage of such API ? Igor can you clarify please ?
>Personally I believe that public API still can be helpful, as it gives user
>an ability to check connection in the specific point in time, even if
>automatic
>ping is implemented (which is more complex and hard-to-maintain feature
>by
Hi Igniters,
I've detected some new issue on TeamCity to be handled. You are more than
welcomed to help.
*New Critical Failure in master Cache (Restarts) 1
https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_CacheRestarts1?branch=%3Cdefault%3E
No changes in the build
*
Personally I believe that public API still can be helpful, as it gives user
an ability to check connection in the specific point in time, even if
automatic
ping is implemented (which is more complex and hard-to-maintain feature
by the way).
Not sure there should be "ping" in API though, maybe
Alexey,
We've benchmarked the whole set of tests tonight in both persistent and
in-memory modes on the current 2.9 branch (with minor tracing optimization
merged). And on our environment, we've got 0-2.5% drop for each benchmark
compared to 2.8.1. I think it is an acceptable result.
So, I'm ok
Hi Charles,
Welcome to Apache Ignite Community!
I added your JIRA account to the contributor list. A following page can
help you to start https://ignite.apache.org/community/contribute.html
Feel free to write a message to dev@ignite.apache.org if you need any
assistance.
2020-09-15 3:28
Ok, I created a ticket [1].
[1] https://issues.apache.org/jira/browse/IGNITE-13450
пн, 14 сент. 2020 г. в 14:59, Юрий :
>
> Dmitrii, seems you are right and we can go with new separate event
>
> пн, 7 сент. 2020 г. в 23:53, Dmitrii Ryabov :
>
> > Any objections to create a separate event, which
24 matches
Mail list logo
