You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Samarth Jain (JIRA)" <ji...@apache.org> on 2015/10/05 20:22:26 UTC

[jira] [Created] (PHOENIX-2307) Build means to set min/max timestamp on store files on region splits.

Samarth Jain created PHOENIX-2307:
-------------------------------------

             Summary: Build means to set min/max timestamp on store files on region splits.
                 Key: PHOENIX-2307
                 URL: https://issues.apache.org/jira/browse/PHOENIX-2307
             Project: Phoenix
          Issue Type: Improvement
            Reporter: Samarth Jain


As part of the work done in PHOENIX-914, we noticed that because of region splits, the time range information cannot be used to filter out the child regions. When splitting a region HBase (understandably) doesn't read every row of the region being split and so it doesn't know the min and max timestamps to add as metadata on the newly created store files.

There possibly could be cases where Phoenix would be able to set the min/ma x timestamps itself. One such scenario being when the part of row key prior to the timestamp hasn't changed in the region that is to be split. We would need HBase APIs to set the min/max timestamp which could be then called in the coprocessor hook for splits.



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