You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Benjamin Lerer (JIRA)" <ji...@apache.org> on 2016/04/12 13:58:25 UTC

[jira] [Created] (CASSANDRA-11556) PER PARTITION LIMIT does not work properly for multi-partition query with ORDER BY

Benjamin Lerer created CASSANDRA-11556:
------------------------------------------

             Summary: PER PARTITION LIMIT does not work properly for multi-partition query with ORDER BY
                 Key: CASSANDRA-11556
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-11556
             Project: Cassandra
          Issue Type: Bug
            Reporter: Benjamin Lerer
            Assignee: Alex Petrov


Multi-partition queries with {{PER PARTITION LIMIT}} with {{ORDER BY}} do not respect the {{PER PARTITION LIMIT}}.

The problem can be reproduced with the following unit test:
{code}
    @Test
    public void testPerPartitionLimitWithMultiPartitionQueryAndOrderBy() throws Throwable
    {
        createTable("CREATE TABLE %s (a int, b int, c int, PRIMARY KEY (a, b))");

        for (int i = 0; i < 5; i++)
        {
            for (int j = 0; j < 5; j++)
            {
                execute("INSERT INTO %s (a, b, c) VALUES (?, ?, ?)", i, j, j);
            }
        }

        assertRows(execute("SELECT * FROM %s WHERE a IN (2, 3) ORDER BY b DESC PER PARTITION LIMIT ?", 2),
                                row(2, 4, 4),
                                row(3, 4, 4),
                                row(2, 3, 3),
                                row(3, 3, 3));
    }
{code} 



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