cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benedict (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-10045) Sparse/Dense decision should be made per-row, not per-file
Date Thu, 27 Aug 2015 09:57:45 GMT


Benedict commented on CASSANDRA-10045:

I added that in in order to debug over cassci, as I have spent more than a day failing to
get dtests to work locally :(   I'll move that to a different branch in future to avoid confusion.

I've traced the problem, to the {{noRowsIterator}} always returning {{PartitionColumns.NONE}}
even if it had a non-empty static row (the fix was possibly in the version you just looked
at, in fact). I've pushed an update with the noise stripped out that is currently validating.

> Sparse/Dense decision should be made per-row, not per-file
> ----------------------------------------------------------
>                 Key: CASSANDRA-10045
>                 URL:
>             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

View raw message