[
https://issues.apache.org/jira/browse/CASSANDRA-3974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13427448#comment-13427448
]
Jeremy Hanna commented on CASSANDRA-3974:
-----------------------------------------
bq. If we're just going to have CF TTL being sugar for clients too lazy to
apply what they want, then I'm not interested.
Also if that client happens to be Pig or Hive, there's not currently a way to
set TTLs. So in that case it's not laziness of the client.
A use case: I don't want to MapReduce over my giant archival column family so
when ingesting data, I'll write to my archival column family and in addition a
column family with a default TTL or however it's implemented, so it would just
be data from the last 30 days.
> Per-CF TTL
> ----------
>
> Key: CASSANDRA-3974
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3974
> Project: Cassandra
> Issue Type: New Feature
> Affects Versions: 1.2
> Reporter: Jonathan Ellis
> Assignee: Kirk True
> Priority: Minor
> Fix For: 1.2
>
> Attachments: trunk-3974.txt, trunk-3974v2.txt, trunk-3974v3.txt,
> trunk-3974v4.txt
>
>
> Per-CF TTL would allow compaction optimizations ("drop an entire sstable's
> worth of expired data") that we can't do with per-column.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
