[
https://issues.apache.org/jira/browse/PHOENIX-2722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15225946#comment-15225946
]
ASF GitHub Bot commented on PHOENIX-2722:
-----------------------------------------
Github user ankitsinghal commented on a diff in the pull request:
https://github.com/apache/phoenix/pull/154#discussion_r58506510
--- Diff:
phoenix-core/src/main/java/org/apache/phoenix/iterate/MergeSortTopNResultIterator.java
---
@@ -79,9 +86,11 @@ public Tuple peek() throws SQLException {
@Override
public Tuple next() throws SQLException {
- if (limit >= 0 && count++ >= limit) {
- return null;
+ while (count < offset) {
+ if (super.next() == null) { return null; }
+ count++;
}
+ if (limit >= 0 && count++ >= limit) { return null; }
--- End diff --
Actually it should count++ only, but there is a bug in offset count ..
which I have updated now.
> 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
> Attachments: PHOENIX-2722.patch, PHOENIX-2722_formatted.patch
>
>
> 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.
> syntax
> {code}
> [ LIMIT { count } ]
> [ OFFSET start [ ROW | ROWS ] ]
> [ FETCH { FIRST | NEXT } [ count ] { ROW | ROWS } ONLY ]
> {code}
> Some new keywords(OFFSET,FETCH,ROW, ROWS,ONLY) are getting introduced so
> users might need to see that they are not using them as column name or
> something.
> WDYT, [~jamestaylor]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
