Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Thu, 19 Dec 2013 17:02:07 +0000 (UTC)
From: "Jonathan Ellis (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12685623.1387470662740.65672.1387472527251@arcas>
In-Reply-To: <JIRA.12685623.1387470662740@arcas>
References: <JIRA.12685623.1387470662740@arcas>
Subject: [jira] [Resolved] (CASSANDRA-6511) extend LIMIT to define offset,
 row_count
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jonathan Ellis resolved CASSANDRA-6511.
---------------------------------------

    Resolution: Won't Fix

OFFSET is inherently O(n) in the number of columns skipped.

> extend LIMIT to define offset, row_count
> ----------------------------------------
>
>                 Key: CASSANDRA-6511
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6511
>             Project: Cassandra
>          Issue Type: New Feature
>            Reporter: Pardeep Singh
>              Labels: cql3, query
>
> Currently I can to do:
> SELECT * FROM top_posts WHERE id="music" LIMIT 10;
> If it was possible to extend the LIMIT clause to:
> [LIMIT {[offset,] row_count | row_count OFFSET offset}]
> SELECT * FROM top_posts WHERE id="music" LIMIT 10, 10;
> Pagination will be possible without using clustering key with less than or greater than.


--
This message was sent by Atlassian JIRA
(v6.1.4#6159)