You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "James Taylor (JIRA)" <ji...@apache.org> on 2014/10/07 00:56:33 UTC

[jira] [Updated] (PHOENIX-1321) Cleanup setting of timestamps when collecting and using stats

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

James Taylor updated PHOENIX-1321:
----------------------------------
    Attachment: PHOENIX-1321_4.patch

> Cleanup setting of timestamps when collecting and using stats
> -------------------------------------------------------------
>
>                 Key: PHOENIX-1321
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-1321
>             Project: Phoenix
>          Issue Type: Sub-task
>            Reporter: James Taylor
>            Assignee: James Taylor
>         Attachments: PHOENIX-1321_4.patch
>
>
> We're currently not using the max timestamp that was passed through the Scan when we do an ANALYZE. In the same way, we're not using the client timestamp when we read the stats and cache them on PTable. The tricky thing is what timestamp to use for the stats when a split or compaction occurs, because in those cases we don't have a user supplied timestamp (if they're managing timestamps themselves).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)