[jira] Resolved: (CASSANDRA-691) get_key_range limit parameter has a smaller range than i32

["Jonathan Ellis (JIRA)" <ji...@apache.org>]

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

Jonathan Ellis resolved CASSANDRA-691.
--------------------------------------

    Resolution: Won't Fix

Yes, to fix a bug in 0.4, the 0.5 code creates a Set of size max_results to handle duplicate removal.  Don't pass a max_results larger than you have enough memory to handle this with (or you'd OOM anyway if you actually got anywhere near that many results...)

> get_key_range limit parameter has a smaller range than i32
> ----------------------------------------------------------
>
>                 Key: CASSANDRA-691
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-691
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 0.5
>         Environment: linux x86
>            Reporter: Hernan Badenes
>            Priority: Minor
>
> get_key_range fails with an exception (TApplicationException("Internal error processing get_key_range")) if the maxResults parameter is any value greater than 134217728 = 0x8000000 . Note that the i32 parameter allows a larger maximum value -- e.g. from Java one one try to pass Integer.MAX_VALUE to obtain all the keys.
> I experience the problem throught thrift, both from java and python. The same code was working on 0.4.2, while this is happening on code just checked out from trunk. I don't think this is a thrift problem, since other calls (e.g. get_slice with a SlicePredicate(SliceRange)) allow MAX_INT to be passed.
> Perhaps the solution is just to document the maximum allowed value in the API.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.