You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@phoenix.apache.org by "Jacob Isaac (Jira)" <ji...@apache.org> on 2019/10/14 16:49:00 UTC

[jira] [Updated] (PHOENIX-5464) Verify that the EMPTY_COLUMN column is updated under various scenarios in hbase.

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

Jacob Isaac updated PHOENIX-5464:
---------------------------------
    Attachment: PHOENIX-5464.master.001.patch

> Verify that the EMPTY_COLUMN column is updated under various scenarios in hbase.
> --------------------------------------------------------------------------------
>
>                 Key: PHOENIX-5464
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-5464
>             Project: Phoenix
>          Issue Type: Sub-task
>            Reporter: Jacob Isaac
>            Assignee: Jacob Isaac
>            Priority: Major
>             Fix For: 4.15.1, 5.1.1
>
>         Attachments: PHOENIX-5464.4.x.HBase1-3.001.patch, PHOENIX-5464.master.001.patch
>
>
> We plan to use the timestamp of the EMPTY_COLUMN to support TTL for views. Since each column in HBase can have a different timestamp depending on when it gets updated. The timestamp of the EMPTY_COLUMN can serve as the timestamp of the row (a row in PHOENIX) and can be used to determine TTL expiration of a row in PHOENIX.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)