[
https://issues.apache.org/jira/browse/PHOENIX-3572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15958093#comment-15958093
]
ASF GitHub Bot commented on PHOENIX-3572:
-----------------------------------------
Github user JamesRTaylor commented on a diff in the pull request:
https://github.com/apache/phoenix/pull/229#discussion_r110057029
--- Diff:
phoenix-core/src/main/java/org/apache/phoenix/compile/QueryPlan.java ---
@@ -59,6 +60,8 @@
* Returns projector used to formulate resultSet row
*/
RowProjector getProjector();
+
+ String getCursorName();
--- End diff --
I think an alternate implementation would be to have a CursorQueryPlan
which wraps another QueryPlan. This would be similar to the way a UnionPlan was
implemented. That way you wouldn't need to litter the other plan
implementations with logic to wrap them with the CursorResultIterator (which
would be brittle if/when new plans are added).
> Support FETCH NEXT| n ROWS from Cursor
> --------------------------------------
>
> Key: PHOENIX-3572
> URL: https://issues.apache.org/jira/browse/PHOENIX-3572
> Project: Phoenix
> Issue Type: Sub-task
> Reporter: Biju Nair
> Assignee: Biju Nair
>
> Implement required changes to support
> - {{DECLARE}} and {{OPEN}} a cursor
> - query {{FETCH NEXT | n ROWS}} from the cursor
> - {{CLOSE}} the cursor
> Based on the feedback in [PR
> #192|https://github.com/apache/phoenix/pull/192], implement the changes using
> {{ResultSet}}.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
