You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2013/01/10 18:52:12 UTC

[jira] [Updated] (CASSANDRA-4833) get_count with 'count' param between 1024 and ~actual column count fails

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

Jonathan Ellis updated CASSANDRA-4833:
--------------------------------------

    Affects Version/s:     (was: 1.1.6)
                           (was: 1.2.0 beta 1)
                       1.1.0

Updating affects-version to 1.1.0 since "this seems to affect all of 1.1," and since the fix caused a regression with TTL data (CASSANDRA-5099).
                
> get_count with 'count' param between 1024 and ~actual column count fails
> ------------------------------------------------------------------------
>
>                 Key: CASSANDRA-4833
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4833
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.1.0
>            Reporter: Tyler Hobbs
>            Assignee: Yuki Morishita
>             Fix For: 1.1.7, 1.2.0 beta 2
>
>         Attachments: 4833-1.1.txt, 4833-1.1-v2.txt, 4833-get-count-repro.py
>
>
> If you run get_count() with the 'count' param of the SliceRange set to a number between 1024 and (approximately) the actual number of columns in the row, something seems to silently fail internally, resulting in a client side timeout.  Using a 'count' param outside of this range (lower or much higher) works just fine.
> This seems to affect all of 1.1 and 1.2.0-beta1, but not 1.0.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira