You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2015/08/11 23:43:45 UTC

[jira] [Commented] (CASSANDRA-10045) Sparse/Dense decision should be made per-row, not per-file

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

Jonathan Ellis commented on CASSANDRA-10045:
--------------------------------------------

Will this change the sstable format?  If not there is no rush to get it in before b1.

> 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)