Agree with Ivan regarding compatibility.
Partition reservation should be opt-in if we decide to proceed.
> is there a real need/benefit from using
> scan queries over primitive SQL queries today
SQL requires additional configuration (QueryEntity) and involves memory and
CPU overhead to maintain
Hi Maksim,
Thank you for looking into this. While fixing wrong/surprising
behavior is very important, I also have some concerns, let's say, from
different angle of view:
1. From a first glance it seems that similar behavior of scan and SQL
queries is a good idea. But is there a real need/benefit
Hi, Igniters!
There is a known issue that ScanQuery on unstable topology returns
incorrect results: duplicates data [1] or fails with an exception [2]. The
reason is ScanQuery doesn't reserve partitions.
IndexQuery shares the same query processing as ScanQuery, and then it is
also affected by
Hello.
Let’s include [1] in 2.12 scope.
After migrations authentication processor to security API we have an issue.
Persistent data region should exists on client node if authentication is
enabled.
It seems very annoying for the users.
[1] https://issues.apache.org/jira/browse/IGNITE-15969
>
