[
https://issues.apache.org/jira/browse/CASSANDRA-10045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14709392#comment-14709392
]
Sylvain Lebresne commented on CASSANDRA-10045:
----------------------------------------------
bq. the previous columns didn't actually exist in the {{CFMetaData}}
To clarify, I meant that change:
{noformat}
-
.newRow("someName").add("val", "someValue")
+
.newRow("name").add("val", "someValue")
{noformat}
This changes the _value_ of the clustering column so shouldn't have anything to
do with declared columns name and that's why the change stroke me as odd. But
looking closer, I doesn't seem that change make any difference for the test so
I don't care.
bq. Will post an update shortly.
If you could link to the CI results when you do so that would be awesome.
> 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 2
>
>
> 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)
