cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Shook (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-7666) Range-segmented sstables
Date Sat, 20 Dec 2014 00:12:13 GMT


Jonathan Shook commented on CASSANDRA-7666:

It might simply be easier to explain to users how it works, relative to DTCS, specifically
because of clearer semantics of segmenting by field values. I believe a similar mechanism
is used in influx for automatically aging out expired time ranges. You could easily see "keep
last N months" style lifecycle management with this too, which wouldn't play well with other
layouts. I'm a fan of DTCS, however the conceptual clarity of this approach is far more appealing.

> Range-segmented sstables
> ------------------------
>                 Key: CASSANDRA-7666
>                 URL:
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: API, Core
>            Reporter: Jonathan Ellis
>            Assignee: Sam Tunnicliffe
>             Fix For: 3.0
> It would be useful to segment sstables by data range (not just token range as envisioned
by CASSANDRA-6696).
> The primary use case is to allow deleting those data ranges for "free" by dropping the
sstables involved.  We should also (possibly as a separate ticket) be able to leverage this
information in query planning to avoid unnecessary sstable reads.
> Relational databases typically call this "partitioning" the table, but obviously we use
that term already for something else:
> Tokutek's take for mongodb:

This message was sent by Atlassian JIRA

View raw message