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

Posted to commits@cassandra.apache.org by "Benedict (JIRA)" <ji...@apache.org> on 2015/07/08 23:34:04 UTC

[jira] [Created] (CASSANDRA-9763) PartitionUpdate must sort() before returning rowCount()

Benedict created CASSANDRA-9763:
-----------------------------------

             Summary: PartitionUpdate must sort() before returning rowCount()
                 Key: CASSANDRA-9763
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9763
             Project: Cassandra
          Issue Type: Bug
          Components: Core
            Reporter: Benedict
            Assignee: Benedict
             Fix For: 3.0.x


PartitionUpdate does not ensure its row count is accurate before reporting it. This can result in, for instance, null records making their way into Memtables because fewer rows were provided than promised.

This patch fixes this, but makes no effort to avoid similar problems. Once the refactor makes its way into mainline, I'll have a look at the hierarchy as a whole. I think it is very likely we can do away with the distinction between btree/array backed implementations, so there are fewer places to introduce these mistakes. The btree has the benefit of being inherently immutable, so these sorts of states cannot be reached.



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