cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (Resolved) (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CASSANDRA-3398) Offset in cassandra-cli for list command
Date Sun, 23 Oct 2011 15:10:32 GMT

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

Jonathan Ellis resolved CASSANDRA-3398.
---------------------------------------

    Resolution: Not A Problem

list already takes an optional start key
                
> Offset in cassandra-cli for list command
> ----------------------------------------
>
>                 Key: CASSANDRA-3398
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3398
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Tools
>    Affects Versions: 1.0.0
>            Reporter: Patrick Julien
>
> If you have a lot of columns per row, it's very easy to get an OOM using the list command
in cassandra-cli.  Listing more and more rows for the purpose of tracking issues is hard because
there isn't an offset that says to skip the first n rows.
> My understanding is that no matter what partition scheme you're using, the rows will
always be at the same offset from the beginning assuming no additional keys were inserted.
> I believe this could be a worthwhile enhancement

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message