[jira] [Updated] (PHOENIX-4179) Use max timestamp of projected cells for cell timestamp returned to client

["James Taylor (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/PHOENIX-4179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

James Taylor updated PHOENIX-4179:
----------------------------------
    Attachment: PHOENIX-4179.patch

Minor change to make timestamp of cell sent back to the client be the "last updated timestamp" instead of somewhat randomly be the timestamp of the first projected cell. This is particular targeted for our index scrutiny which stores this timestamp for later diagnosis. Please review, [~vincentpoon].

> Use max timestamp of projected cells for cell timestamp returned to client
> --------------------------------------------------------------------------
>
>                 Key: PHOENIX-4179
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-4179
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: James Taylor
>            Assignee: James Taylor
>             Fix For: 4.12.0
>
>         Attachments: PHOENIX-4179.patch
>
>
> The timestamp that we use for the cell that gets serialized back to the client is somewhat random, as it'll be the timestamp of the first cell. Instead, we should use the max timestamp we see across all cells that are projected.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)