[
https://issues.apache.org/jira/browse/PHOENIX-6204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17219352#comment-17219352
]
Chinmay Kulkarni commented on PHOENIX-6204:
-------------------------------------------
[~kozdemir] I see that you had suggested using a hint like "TIMESTAMP" in
PHOENIX-5018 (see this
[comment|https://issues.apache.org/jira/browse/PHOENIX-5018?focusedCommentId=16734512&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16734512])
but another approach was later chosen. Is there a downside to implementing
this Jira the way you had suggested in your comment above?
> Provide a way to preserve HBase cell timestamps when running UPSERT SELECT
> statements
> -------------------------------------------------------------------------------------
>
> Key: PHOENIX-6204
> URL: https://issues.apache.org/jira/browse/PHOENIX-6204
> Project: Phoenix
> Issue Type: New Feature
> Affects Versions: 4.15.0
> Reporter: Chinmay Kulkarni
> Priority: Major
>
> Today when we run an UPSERT SELECT statement, the data is upserted with the
> current wall clock time rather than using the timestamp of the cells being
> read via the SELECT statement. In some cases this is favorable, but in others
> it is not.
> Providing a way to do an UPSERT SELECT in which upserts use the HBase
> timestamp of the cells being read is a useful feature.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
