Jan Fernando created PHOENIX-3725:
-------------------------------------
Summary: Add support for per VIEW level TTLs in addition to table
level TTLs
Key: PHOENIX-3725
URL: https://issues.apache.org/jira/browse/PHOENIX-3725
Project: Phoenix
Issue Type: New Feature
Reporter: Jan Fernando
We are seeing more and more use cases where it would be very helpful to declare
a TTL for data at the View level instead of the table level. We have several
use cases where a shared Phoenix table is partitioned by views and each view
has some shared columns with the base table and it's own unique columns. In
these cases it's not possible to declare a TTL for data at the table level as
each view may warrant a different TTL.
As a result, enforcement of a TTL for data relies on custom jobs that query the
data that has expired and then deletes them via SQL. This has 2 major
disadvantages a) developers have to write a custom job and b) we can
potentially create a lot of delete markers in HBase.
>From an end-user perspective it would really simplify the development
>experience if users could instead simply declare a TTL on the view and let
>Phoenix/HBase take care of deletion at compaction time.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
