[
https://issues.apache.org/jira/browse/CASSANDRA-3974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13494329#comment-13494329
]
Jonathan Ellis commented on CASSANDRA-3974:
-------------------------------------------
bq. it does feel a bit fragile that some future internal code could too easily
add an ExpiringColumn though ColumnFamily.addColumn(IColumn)
Tracing and unit tests (via Util.expiringColumn) already use this method.
Should we make the constructors private and expose a factory method that
requires the metadata?
> 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.0 beta 1
> Reporter: Jonathan Ellis
> Assignee: Kirk True
> Priority: Minor
> Fix For: 1.2.0 rc1
>
> Attachments: trunk-3974.txt, trunk-3974v2.txt, trunk-3974v3.txt,
> trunk-3974v4.txt, trunk-3974v5.txt, trunk-3974v6.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
For more information on JIRA, see: http://www.atlassian.com/software/jira
