phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Taylor (JIRA)" <>
Subject [jira] [Commented] (PHOENIX-1240) Add TTL to SYSTEM.TRACING_STATS table
Date Tue, 25 Nov 2014 02:16:12 GMT


James Taylor commented on PHOENIX-1240:

You should be able to specify column family properties in both CREATE TABLE and ALTER TABLE.
The properties for CREATE TABLE apply to either a) the HTableDescriptor or b) the HColumnDescriptor,
or c) the Phoenix table. They don't apply to a row, though. Neither (a) nor (b) are supported
through the ALTER TABLE statement, but Samarth is working on fixing that.

I'd definitely classify TTL as "advanced usage". As I mentioned, it's fine to have a TTL on
a column family, but not if it's the column family that contains the empty key value. However,
if the table has a secondary index, the TTL would cause the table and index to get out of
sync. In theory, you could have an "eventually" (or maybe "approximate") consistent view if
you had the same TTL on both. But this would be pretty crazy.

So I suppose the question that we should answer is do we want to pick and choose HBase features
that are "too risky" and not allow users to use them? Or should we have a "use at your own
risk" classification? Not sure what the right answer is - users will always be able to got
behind the back of Phoenix and make these changes through the HBase shell using the admin

> -------------------------------------
>                 Key: PHOENIX-1240
>                 URL:
>             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

View raw message