[
https://issues.apache.org/jira/browse/PHOENIX-5629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17020630#comment-17020630
]
Tanuj Khurana commented on PHOENIX-5629:
----------------------------------------
At the Hbase level, yes we have a cell per column. The default behavior that I
am seeing is that in the rpc handler the phoenix BaseScannerRegionObserver
coprocessor is combining all the projected cells into a single cell that is
returned to the client. The timestamp of that cell is the max timestamp of all
the projected cells. This Jira
[PHOENIX-4179|https://issues.apache.org/jira/browse/PHOENIX-4179] talks about
the max timestamp change.
> Phoenix Function to Return HBase Timestamp of Column Cell
> ---------------------------------------------------------
>
> Key: PHOENIX-5629
> URL: https://issues.apache.org/jira/browse/PHOENIX-5629
> Project: Phoenix
> Issue Type: New Feature
> Reporter: Geoffrey Jacoby
> Assignee: Tanuj Khurana
> Priority: Major
> Fix For: 5.1.0, 4.16.0
>
>
> t's occasionally useful when diagnosing an issue with Phoenix to be able to
> easily look up the HBase timestamp of the HBase Cell returned by a Phoenix
> query.
> For example:
> SELECT ROW_TIMESTAMP(Column1) FROM Table1 WHERE Column1 = 'SomeValue'
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
