Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Thu, 4 Sep 2014 17:26:52 +0000 (UTC)
From: "Mikhail Stepura (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12726057.1404820686000.19582.1409851612236@Atlassian.JIRA>
In-Reply-To: <JIRA.12726057.1404820686000@Atlassian.JIRA>
References: <JIRA.12726057.1404820686000@Atlassian.JIRA>
 <JIRA.12726057.1404820686558@arcas>
Subject: [jira] [Updated] (CASSANDRA-7514) Support paging in cqlsh
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Mikhail Stepura updated CASSANDRA-7514:
---------------------------------------
    Attachment: CASSANDRA-2.1-7514.patch

I'm attaching a patch with new "PAGING" command

> Support paging in cqlsh
> -----------------------
>
>                 Key: CASSANDRA-7514
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7514
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Sylvain Lebresne
>            Assignee: Mikhail Stepura
>            Priority: Minor
>              Labels: cqlsh
>             Fix For: 2.1.1
>
>         Attachments: CASSANDRA-2.1-7514.patch
>
>
> Once we've switch cqlsh to use the python driver 2.x (CASSANDRA-7506), we should also make it use paging. Currently cqlsh adds an implicit limit which is kind of ugly. Instead we should use some reasonably small page size (100 is probably fine) and display one page at a time, adding some "NEXT" command to query/display following pages.


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