cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aleksey Yeschenko (JIRA)" <>
Subject [jira] [Resolved] (CASSANDRA-7115) Column Family (Table) partitioning with column keys as partition keys (Sorta TTLed Table)
Date Fri, 18 Mar 2016 21:05:33 GMT


Aleksey Yeschenko resolved CASSANDRA-7115.
    Resolution: Won't Fix

This could work, but arguably not worth the extra complexity. There are many ways to expire-cleanup
data already, and you can model around it if necessary.

> Column Family (Table) partitioning with column keys as partition keys (Sorta TTLed Table)
> -----------------------------------------------------------------------------------------
>                 Key: CASSANDRA-7115
>                 URL:
>             Project: Cassandra
>          Issue Type: New Feature
>            Reporter: Haebin Na
>            Priority: Minor
>              Labels: features
> We need a better solution to expire columns than TTLed columns.
> If you set TTL 6 months for a column in a frequently updated(deleted, yes, this is anti-pattern)
wide row, it is not likely to be deleted since the row would be highly fragmented.
> In order to solve the problem above, I suggest partitioning column family (table) with
column key (column1) as partition key.
> It is like a set of column families (tables) which share the same structure and cover
certain range of columns per CF. This means that a row is deterministically fragmented by
column key.
> If you use timestamp like column key, then you would be able to truncate specific partition
(a sub-table or CF with specific range) if it is older than certain age easily without worrying
about zombie tombstones. 
> It is not optimal to have many column families, yet even with small set like by biyearly
or quarterly, it could be whole lot more efficient than TTLed columns.
> What do you think?

This message was sent by Atlassian JIRA

View raw message