[
https://issues.apache.org/jira/browse/PHOENIX-2722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15173314#comment-15173314
]
Ankit Singhal commented on PHOENIX-2722:
----------------------------------------
Although offset for queries threaded in parallel(including orderby) would not
be optimized as serial queries because offset can not pushed down to servers
for them.
but it's just help the user not to call next() offset number of times instead
get some optimization abstracted under a SQL construct.
Users can use it for random access of pages or paged queries wherever RVC is
not possible.
what about including this construct with the details about the implementation
in the documentation and user can use it as per the optimization?
> support mysql "limit,offset" clauses
> -------------------------------------
>
> Key: PHOENIX-2722
> URL: https://issues.apache.org/jira/browse/PHOENIX-2722
> Project: Phoenix
> Issue Type: New Feature
> Reporter: Ankit Singhal
> Assignee: Ankit Singhal
> Priority: Minor
>
> For serial query(query with “serial" hint or “limit" without "order by”), we
> can limit each scan(using page filter) to “limit+offset” instead of limit
> earlier.
> And then, for all queries, we can forward the relevant client iterators to
> the offset provided and then return the result.
> WDYT, [~jamestaylor]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
