[
https://issues.apache.org/jira/browse/PHOENIX-1240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14244639#comment-14244639
]
Alicia Ying Shu edited comment on PHOENIX-1240 at 12/12/14 7:17 PM:
--------------------------------------------------------------------
[~giacomotaylor] Looking through CreateTableIT, when setting TTL for the table,
all the column families' TTL are set to the same number, not just the default
column family. Do we want to keep the same behavior?
Also if setting TTL for both table and column families in the same Alter Table
SQL, which number should we keep?
ALTER TABLE Test SET TTL=20, a.col1=100, b.col2=90;
I will check in TTL specific unit tests using this Jira.
was (Author: aliciashu):
[~giacomotaylor] Looking through CreateTableIT, when setting TTL for the table,
all the column families' TTL are set to the same number, not just the default
column family. Do we want to keep the same behavior?
Also if setting TTL for both table and column family, which number should we
keep?
ALTER TABLE Test SET TTL=20, a.col1=100;
I will check in TTL specific unit tests using this Jira.
> Add TTL to SYSTEM.TRACING_STATS table
> -------------------------------------
>
> Key: PHOENIX-1240
> URL: https://issues.apache.org/jira/browse/PHOENIX-1240
> Project: Phoenix
> Issue Type: Sub-task
> Affects Versions: 5.0.0, 4.1.1
> Reporter: Jesse Yates
> Assignee: Alicia Ying Shu
> Fix For: 5.0.0, 4.1.1
>
> Attachments: PHOENIX-1240.patch
>
>
> Tracing table should have a configurable TTL on it, so the table doesn't fill
> up with too much data.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
