Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Fri, 24 Oct 2014 15:18:34 +0000 (UTC)
From: "Stuart Gunter (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12750371.1414163885000.331378.1414163914211@Atlassian.JIRA>
In-Reply-To: <JIRA.12750371.1414163885000@Atlassian.JIRA>
References: <JIRA.12750371.1414163885000@Atlassian.JIRA>
 <JIRA.12750371.1414163885432@arcas>
Subject: [jira] [Created] (CASSANDRA-8185) Removing the last item from a
 collection removes the entire row
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Stuart Gunter created CASSANDRA-8185:
----------------------------------------

             Summary: Removing the last item from a collection removes the entire row
                 Key: CASSANDRA-8185
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8185
             Project: Cassandra
          Issue Type: Bug
          Components: Core
         Environment: Mac OS X Yosemite
JDK 8u25
            Reporter: Stuart Gunter
            Priority: Minor


When removing the last item from a list or set (and I assume the same applies to maps), the entire row is deleted rather than just that last item.

I've only tested this in cases where the collection column is the only non-PK column, but it is definitely a change between v2.0.5 and v2.0.6. I've looked through the 2.0.6 release notes and issues and can't find any item that might describe this, so I assume it's not an intended change. If such an issue exists, I've probably just missed it, so apologies in advance.

I've created a very simple project to reproduce the issue. If you clone the repo and run it in two different modes (the README explains how to do this with preconfigured Maven profiles), you will see the tests that pass on v2.0.5 and fail on v2.0.6.

Repo: https://github.com/stuartgunter/cassandra-2.0.6-bug


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