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] [Commented] (CASSANDRA-10045) Sparse/Dense decision should be made per-row, not per-file
Date Wed, 12 Aug 2015 08:24:45 GMT

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

Aleksey Yeschenko commented on CASSANDRA-10045:
-----------------------------------------------

I don't follow how and why. There will be some other, incompatible changes between b1 and
rc1. We never guaranteed compatibility between betas and rcs - even between rcs and GA. With
the former, and I don't see why we ever should, with the latter - it would certainly be nice,
but 3.0.0 is definitely not the time to start with that policy.

> 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