Yes, it's expected that query performance would degrade as the offset increases. The best Phoenix can do for OFFSET is to scan the rows and count them until the offset is reached. Use the row value constructor technique instead to prevent this: https://phoenix.apache.
org/paged.htmlOn Thu, May 18, 2017 at 6:18 AM, Sumanta Gh <firstname.lastname@example.org> wrote:Thanks Rafa.This is working perfectly fine with 4.10.Are the offset and limit enforced on client side? I find the performance of query gradually degrades as I increase the offset value.Regards
-----rafa <email@example.com> wrote: -----