Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Tue, 3 Feb 2015 22:38:35 +0000 (UTC)
From: "Tyler Hobbs (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12772175.1423003086000.247695.1423003115298@Atlassian.JIRA>
In-Reply-To: <JIRA.12772175.1423003086000@Atlassian.JIRA>
References: <JIRA.12772175.1423003086000@Atlassian.JIRA>
 <JIRA.12772175.1423003086218@arcas>
Subject: [jira] [Created] (CASSANDRA-8733) List prepend reverses item order
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Tyler Hobbs created CASSANDRA-8733:
--------------------------------------

             Summary: List prepend reverses item order
                 Key: CASSANDRA-8733
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8733
             Project: Cassandra
          Issue Type: Bug
          Components: Core
            Reporter: Tyler Hobbs
            Assignee: Tyler Hobbs
             Fix For: 2.1.3, 2.0.13


If you prepend a list of items to a list collection, it will reverse the order of the prepend-list:

{noformat}
cqlsh:ks1> UPDATE foobar SET b = [2, 3] WHERE a = 0;
cqlsh:ks1> select * from foobar;

 a | b
---+--------
 0 | [2, 3]

(1 rows)
cqlsh:ks1> UPDATE foobar SET b = [0, 1] + b WHERE a = 0;
cqlsh:ks1> select * from foobar;

 a | b
---+--------------
 0 | [1, 0, 2, 3]

(1 rows)
{noformat}

This is because we're going through the prepend-list in a normal-order for-loop and prepending each time (in Lists.Prepender).


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