Re: SQL query timeout: in progress or abandoned

2019-11-08 Thread Saikat Maitra
Pavel Tupitsyn, Igor Sapego I wanted to connect and confirm on changes for this PR. https://github.com/apache/ignite/pull/6490 Do you think keeping the change for PlatformConfigurationUtils.java will cause regression on the .NET component or C++ components? Jira :

Re: Calcite based SQL query engine. Local queries

2019-11-08 Thread Denis Magda
Take the amount of cashback calculation or payments authorization as examples of compute tasks with local SQL. In the first case, all transactions are collocated per account and a bank needs to calculate the cashback monthly by broadcasting the task that executes special logic across all accounts

Re: Calcite based SQL query engine. Local queries

2019-11-08 Thread Dmitriy Pavlov
Yes, I understand that it is straightforward and, may be, naive approach. Which is why I'm asking how to do map-reduce on cache C data in Ignite with proper partition pinning. About Predefined/Implemented aggregate - I'm not sure I agree that we can predict everything. It is real perk of Ignite

Re: Calcite based SQL query engine. Local queries

2019-11-08 Thread Ivan Pavlukhin
Dmitriy, First, what kind of cumulative metric can it be? A lot of cumulative metrics can be compared using SQL. MIN, MAX, AVG are simple ones. For more complex ones I can think about user-define aggregate functions (UDAF). We do not have them in Ignite so far, but can introduce them. Second,

Re: Calcite based SQL query engine. Local queries

2019-11-08 Thread Dmitriy Pavlov
Hi Ivan, Igniters, imagine you need to scan all entities in the cluster. Ideally, you don't want to de-serialize all of entries, so you can use withKeepBinary(). e.g. you need a couple of fields and get some cumulative metric on this data. You can send compute to all cluster nodes and run there

Re: Review for IGNITE-12300

2019-11-08 Thread Denis Garus
Hi, Ilya! I've fixed the flaky test. Could you have a look? Thank you! чт, 7 нояб. 2019 г. в 17:12, Ilya Kasnacheev : > 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, > --