[
https://issues.apache.org/jira/browse/PHOENIX-5742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17064724#comment-17064724
]
Chen Feng commented on PHOENIX-5742:
------------------------------------
We used a hint to implement sql level SCN without adding new syntax, see
PHOENIX-5405.
> Statement-Level SCN
> -------------------
>
> Key: PHOENIX-5742
> URL: https://issues.apache.org/jira/browse/PHOENIX-5742
> Project: Phoenix
> Issue Type: New Feature
> Reporter: Geoffrey Jacoby
> Priority: Major
>
> Use cases that need to do a lot of lookback queries to different times might
> want to set SCN at a SQL statement level rather than maintaining a pool of
> connections, each at a different SCN.
> This would require both new SQL syntax, as well as changes to the client code
> to grab the SCN from the statement, which would check both itself and the
> connection. In the event of a conflict between the statement and the
> connection, the statement would control.
> Perhaps we could use the Oracle syntax, which is AS OF <timestamp> after the
> FROM clause but before the WHERE.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
