Hello Igniters, Dmitriy,
Congrats, Dmitriy!
I hope that a board's approval is just a formal step :)
Thanks,
S.
чт, 7 нояб. 2019 г. в 10:52, Ivan Pavlukhin :
> Great news!
>
> Dmitriy my congratulations! I really believe that it is the proper
> decision today and will make a great positive impac
Denis, Stephen,
Running a local query in a broadcast closure won't work on changing
topology. We specifically added an affinityCall method to the compute API
in order to pin a partition to prevent its moving and eviction throughout
the task execution. Therefore, the query inside an affinityCall is
Dmitry, my congratulations!
This is a clear sign that you are moving in the right direction.
Good luck!
чт, 7 нояб. 2019 г. в 11:12, Вячеслав Коптилин :
> Hello Igniters, Dmitriy,
>
> Congrats, Dmitriy!
> I hope that a board's approval is just a formal step :)
>
> Thanks,
> S.
>
> чт, 7 нояб. 20
Hello, Igniters!
I've raised the PR [1] for the issue [2].
Could somebody review it?
1. https://github.com/apache/ignite/pull/7017
2. https://issues.apache.org/jira/browse/IGNITE-12300
+1 to Alexey's concerns.
Local SQL query mode is error prone, as a query executes over non-predicted
set of partitions.
Using local mode with deep SQL execution model understanding will lead to
inconsistent result.
Just imagine if we add a note to documentation that "in case of local SQL
user res
Dmitriy, congratulations!
> On 7 Nov 2019, at 12:06, Николай Кулагин wrote:
>
> Dmitry, my congratulations!
>
> This is a clear sign that you are moving in the right direction.
> Good luck!
>
> чт, 7 нояб. 2019 г. в 11:12, Вячеслав Коптилин :
>
>> Hello Igniters, Dmitriy,
>>
>> Congrats, Dm
I made a (bad) assumption that this would also affect queries against
partitions. If “setLocal()” goes away but “setPartitions()” remains I’m happy.
What I would say is that the “broadcast / local” method is one I see fairly
often. Do we need to do a better job educating people of the “correct”
Dmitry, congrats, we will wait the Community roadmap from you and will be
happy to start discussion about that In asf slack or on dev-list!
чт, 7 нояб. 2019 г., 12:27 Petr Ivanov :
> Dmitriy, congratulations!
>
>
> > On 7 Nov 2019, at 12:06, Николай Кулагин
> wrote:
> >
> > Dmitry, my congratul
Stanilovsky Evgeny created IGNITE-12353:
---
Summary: Need to have additional sql benchmarks which covers Date
types and inlining usage.
Key: IGNITE-12353
URL: https://issues.apache.org/jira/browse/IGNITE-12353
Stephen,
In my understanding we need to do a better job to realize use-cases of
Compute + LocalSQL ourselves.
Ideally smart optimizer should do the best job of query deployment.
чт, 7 нояб. 2019 г. в 13:04, Stephen Darlington
:
>
> I made a (bad) assumption that this would also affect queries ag
Hello!
I will re-run tests against fresh master, and then commit if they pass.
For some reason, when I run it locally, it starts to use persistence, do
you have ideas why that would happen?
It also seems to me that
org.apache.ignite.internal.processors.security.compute.closure.ComputeTaskCancelR
Hi, Ilya!
Thank you for the review!
> For some reason, when I run it locally, it starts to use persistence, do
> you have ideas why that would happen?
The reason is "Authentication can be enabled only for cluster with enabled
persistence." [1]
> It also seems to me that
>
org.apache.ignite.inte
Hello!
I can see that, but for some reason I can see a lot of disk I/O while
running this test. Is it possible to only use persistence for auth
purposes, but keep data in-memory?
I have commented JIRA with example of test failure.
Regards,
--
Ilya Kasnacheev
чт, 7 нояб. 2019 г. в 15:36, Denis
Hello!
Unfortunately, the use case of this fix is still not clear. Can you please
introduce a test which will show which capacity is added here? Are you sure
it will not break any existing deployments where SQL is used together with
nested objects?
Regards,
--
Ilya Kasnacheev
ср, 6 нояб. 2019
>> but keep data in-memory?
I don't use any data in tests for this issue; only compute task.
>> I have commented JIRA with example of test failure.
Unfortunately, I don't see your comment in JIRA [1].
1. https://issues.apache.org/jira/browse/IGNITE-12300
чт, 7 нояб. 2019 г. в 15:45, Ilya Kas
> Yes, we can have measurement units in description, but external tool will
be forced to parse textual representation of units.
We do not know anything about that tools. What kind of units they
support? What kind of actions can be done with measurement on the
external tool side? We can only guess
Stephen,
All metrics will be local for node. Cluster wide metric is some
aggregation which could and must be done by special tools not Ignite.
We already have dozen cluster wide but meaningless metrics and a lot
of code for aggregation. It just isn't our job. All cluster wide
metrics will be remo
Hello!
When I run this test, each case takes 10-40 seconds of hardcore disk usage
for some reason.
Oops, sorry. I have just commented your ticket.
Regards,
--
Ilya Kasnacheev
чт, 7 нояб. 2019 г. в 16:18, Denis Garus :
> >> but keep data in-memory?
>
> I don't use any data in tests for this i
Maxim,
A side note - we did not cut the 2.8 branch yet, did we?
This information is not reflected on the release page and I just realized
that it is hard to choose a fix version for a ticket that is being merged
to master when release scope is being finalized. This moment is covered
neither in th
Alexey,
Not yet. I will announce the release branch cutting stage with a
separate post, probably, for a one week before the cut. No one will
not miss it for sure.
Currently, all issues can safely be pinned to 2.8 release, but for
huge issues\features (e.g. `baseline topology`, `persistence`) whi
Hi Folks,
Thank you, it would be a great honor for me to serve in this role. And I
really surprised by this community decision (other PMC members have a huge
contribution to the project in different aspects and they
all deserve recognition).
But it is a little bit early for congrats since the ASF
Folks,
See our compute tasks as an advanced version of stored procedures that let
the users code the logic of various complexity with Java, .NET or C++ (and
not with PL/SQL). The logic can use a combination of APIs (key-value, SQL,
etc.) to access data both locally and remotely while being execute
Saikat Maitra created IGNITE-12354:
--
Summary: QueryTimeoutException need to be added to differentiate
query is cancelled due to timeout
Key: IGNITE-12354
URL: https://issues.apache.org/jira/browse/IGNITE-12354
Denis,
To make things really clearer we need to provide some concrete example
of Compute + LocalSQL and reason about it to figure out whether
"smart" SQL engine can deliver the same (or better) results or not.
пт, 8 нояб. 2019 г. в 01:48, Denis Magda :
>
> Folks,
>
> See our compute tasks as an a
24 matches
Mail list logo
