cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aleksey Yeschenko (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CASSANDRA-7666) Range-segmented sstables
Date Thu, 02 Jun 2016 16:52:59 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-7666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Aleksey Yeschenko resolved CASSANDRA-7666.
------------------------------------------
       Resolution: Later
    Fix Version/s:     (was: 3.x)

bq. I think that it's sufficient to let this be dormant until or unless it is needed to support
other features. DTCS covers most of the immediate benefit.

+1

> Range-segmented sstables
> ------------------------
>
>                 Key: CASSANDRA-7666
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7666
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: CQL
>            Reporter: Jonathan Ellis
>              Labels: dense-storage
>
> 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: http://www.postgresql.org/docs/9.1/static/ddl-partitioning.html
> Tokutek's take for mongodb: http://docs.tokutek.com/tokumx/tokumx-partitioned-collections.html



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message