Optimize key-range queries in pull queries

Open agavra opened this issue 5 years ago • 3 comments

Similar to #5850, but optimized for the scenario where the predicate is a range query on the key field. As part of this ticket, delivering some type of performance benchmarking is included.

Aug 26 '20 21:08 agavra

Has it already been removed?

Nov 02 '20 03:11 koolay

Update - table scans are now a proxy for this: you can issue a range query but it will result in a full table scan. The scope of this ticket is now to leverage the key index to make it more performant.

Mar 02 '21 17:03 agavra

is this enhancement ready ? @patrickstuedi @agavra

Sep 14 '24 07:09 Taymindis