[
https://issues.apache.org/jira/browse/PHOENIX-5405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16900656#comment-16900656
]
Chen Feng commented on PHOENIX-5405:
------------------------------------
[~jamestaylor] You are right, I do agree the this design is bad on the
principle of avoiding passing data in a hint.
We are facing a situation that a connection pool is inited at the beginning. If
we want to open a new connection, we should close and re-create connections for
different time ranges, which involves more complexity in our system, especially
for multi-thread parallelism. In this case, using hint is more convenient.
> 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)
