GitHub user anirudha opened a pull request:

    https://github.com/apache/phoenix/pull/192

    Phoenix Cursors implementation

    //todo

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/bloomberg/phoenix cursors_snapshot

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/phoenix/pull/192.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #192
    
----
commit 1c39e4b109cbddaf2c5d4d841adcc98f8d6ab401
Author: Gabriel Jimenez <[email protected]>
Date:   2016-08-16T17:59:52Z

    Parsing module for the Cursor feature.
    Also added a new test CursorParserTest

commit d6d4b180c6cc3dc111aad8b3f98d95f22d3b1ef8
Author: Gabriel Jimenez <[email protected]>
Date:   2016-08-16T19:20:13Z

    Compiler module for the Cursor Feature.
    
    Main changes were to PhoenixStatement and compilers, but there needed to be 
changes to the subclasses of QueryPlan.

commit d691cf2e750c7bbbfaad758dfa9df816eb8f3bb0
Author: Gabriel Jimenez <[email protected]>
Date:   2016-08-16T19:44:07Z

    Complete functionality of the Cursor feature.
    
    New end to end test cases added for Cursors in 
'CursorWithRowValueConstructorIT.java'.

commit 445c029f8c97616c2b39001ce1fee17a73a54016
Author: Gabriel Jimenez <[email protected]>
Date:   2016-08-17T21:33:13Z

    New STATIC option for the cursor feature, 'STATIC' keyword. Mirrors 
standard SQL definition of cursor behavior for STATIC option. This means 
results fetched by the cursor will not reflect changes made to the data after 
opening the cursor. Current implementation does not make a copy of the data, 
but rather uses the ROW_TIMESTAMP pseudo column. As a result, to use the STATIC 
option the target table must have designated a column as ROW_TIMESTAMP.

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to