You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Sylvain Lebresne (JIRA)" <ji...@apache.org> on 2015/09/04 15:49:45 UTC

[jira] [Resolved] (CASSANDRA-10220) Memtables do not handle column changes for their PartitionColumns

     [ https://issues.apache.org/jira/browse/CASSANDRA-10220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sylvain Lebresne resolved CASSANDRA-10220.
------------------------------------------
    Resolution: Fixed

Alright, cassci seems to be happy (there was one timeout during the unit test, but that test passed multiple time locally, though is a somewhat long test (for a unit test) so pretty sure this was just cassci being slow. ).

> Memtables do not handle column changes for their PartitionColumns
> -----------------------------------------------------------------
>
>                 Key: CASSANDRA-10220
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10220
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: Benedict
>            Assignee: Sylvain Lebresne
>             Fix For: 3.0.0 rc1
>
>
> There are a couple of inherited issues around the {{PartitionColumns}} in {{AbstractBTreePartition}}. Firstly, we do not always return these columns, but sometimes the metadata columns. Secondly, the columns cannot be updated with new columns, and the metadata columns will not show dropped columns. This should most likely be moved into the {{Holder}}, and updated along with any other updates.



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