cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benedict (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-10045) Sparse/Dense decision should be made per-row, not per-file
Date Wed, 12 Aug 2015 08:20:45 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-10045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14693110#comment-14693110
] 

Benedict commented on CASSANDRA-10045:
--------------------------------------

But it might need an sstable version bump and code to cope with both versions sticking around,
no? At least, that's the impression I got from prioritization of other serialization ticket
prioritizations, and would be preferable to avoid.


> Sparse/Dense decision should be made per-row, not per-file
> ----------------------------------------------------------
>
>                 Key: CASSANDRA-10045
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10045
>             Project: Cassandra
>          Issue Type: Sub-task
>          Components: Core
>            Reporter: Benedict
>            Assignee: Benedict
>            Priority: Minor
>             Fix For: 3.0 beta 1
>
>
> Marking this as beta 1 in the hope I have time to rustle it up and get it reviewed beforehand.
If I do not, I will let it slide, but our behaviour right now is not brilliant for workloads
with a variance in density, and it should not be challenging to make a more targeted decision.
> We can also make use of CASSANDRA-9894 to make column encoding more efficient in many,
even dense, cases.



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

Mime
View raw message