[
https://issues.apache.org/jira/browse/PHOENIX-5405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16900696#comment-16900696
]
Chen Feng commented on PHOENIX-5405:
------------------------------------
No, just plain query connection. This is a legacy system used JDBC previously
and switched to Phoenix with minimal code change.
We'll do a test on re-creating connection every time and using hint later.
BTW, you can close this issue since this patch looks unacceptable in hint.
We'll see other possible ways like using time range as a query parameter and
parsing it.
> Enable timerange in sql hint
> ----------------------------
>
> Key: PHOENIX-5405
> URL: https://issues.apache.org/jira/browse/PHOENIX-5405
> Project: Phoenix
> Issue Type: Improvement
> Reporter: Chen Feng
> Priority: Minor
> Attachments: PHOENIX-5405-v1.patch, PHOENIX-5405-v2.patch,
> PHOENIX-5405-v3.patch
>
>
> PHOENIX-914 enabled Native HBase timestamp support to optimize date range
> queries in Phoenix.
> However, the end time is set at the beginning of connection. For a long term
> connection, we cannot change SCN during processing.
> If we have knowledge of underly HBase timestamp, we can use a connection-free
> way to query the target data by adding a hint in sql.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
