[
https://issues.apache.org/jira/browse/PHOENIX-5464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16951415#comment-16951415
]
Hudson commented on PHOENIX-5464:
---------------------------------
SUCCESS: Integrated in Jenkins build Phoenix-4.x-HBase-1.5 #160 (See
[https://builds.apache.org/job/Phoenix-4.x-HBase-1.5/160/])
PHOENIX-5464 Verify that the EMPTY_COLUMN column is updated under (kadir: rev
80652765905fbe4f3e48a92af083e2f8aee907d1)
* (add)
phoenix-core/src/test/java/org/apache/phoenix/query/PhoenixTestBuilder.java
* (add) phoenix-core/src/it/java/org/apache/phoenix/end2end/EmptyColumnIT.java
> 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)
