cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CASSANDRA-691) get_key_range limit parameter has a smaller range than i32
Date Wed, 13 Jan 2010 15:58:54 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12799797#action_12799797
] 

Jonathan Ellis commented on CASSANDRA-691:
------------------------------------------

allowing you to OOM your server by requesting more rows than you have memory for is more of
a tradeoff than a feature.

> 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.


Mime
View raw message