You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Piotr Kołaczkowski (JIRA)" <ji...@apache.org> on 2012/11/06 16:56:11 UTC
[jira] [Created] (CASSANDRA-4919) StorageProxy.getRangeSlice
sometimes returns incorrect number of columns
Piotr Kołaczkowski created CASSANDRA-4919:
---------------------------------------------
Summary: StorageProxy.getRangeSlice sometimes returns incorrect number of columns
Key: CASSANDRA-4919
URL: https://issues.apache.org/jira/browse/CASSANDRA-4919
Project: Cassandra
Issue Type: Bug
Affects Versions: 1.1.6
Reporter: Piotr Kołaczkowski
Assignee: Piotr Kołaczkowski
When deployed on a single node, number of columns is correct.
When deployed on a cluster, total number of returned columns is slightly lower than desired.
--
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
[jira] [Updated] (CASSANDRA-4919) StorageProxy.getRangeSlice
sometimes returns incorrect number of columns
Posted by "Piotr Kołaczkowski (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-4919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Piotr Kołaczkowski updated CASSANDRA-4919:
------------------------------------------
Attachment: 0001-Fix-getRangeSlice-paging-reset-predicate-after-fetch.patch
Attaching a patch fixing paged column iteration.
> StorageProxy.getRangeSlice sometimes returns incorrect number of columns
> ------------------------------------------------------------------------
>
> Key: CASSANDRA-4919
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4919
> Project: Cassandra
> Issue Type: Bug
> Affects Versions: 1.1.6
> Reporter: Piotr Kołaczkowski
> Assignee: Piotr Kołaczkowski
> Attachments: 0001-Fix-getRangeSlice-paging-reset-predicate-after-fetch.patch
>
>
> When deployed on a single node, number of columns is correct.
> When deployed on a cluster, total number of returned columns is slightly lower than desired.
--
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
[jira] [Updated] (CASSANDRA-4919) StorageProxy.getRangeSlice
sometimes returns incorrect number of columns
Posted by "Sylvain Lebresne (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-4919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sylvain Lebresne updated CASSANDRA-4919:
----------------------------------------
Fix Version/s: 1.2.0
1.1.7
> StorageProxy.getRangeSlice sometimes returns incorrect number of columns
> ------------------------------------------------------------------------
>
> Key: CASSANDRA-4919
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4919
> Project: Cassandra
> Issue Type: Bug
> Affects Versions: 1.1.6
> Reporter: Piotr Kołaczkowski
> Assignee: Piotr Kołaczkowski
> Fix For: 1.1.7, 1.2.0
>
> Attachments: 0001-Fix-getRangeSlice-paging-reset-predicate-after-fetch.patch
>
>
> When deployed on a single node, number of columns is correct.
> When deployed on a cluster, total number of returned columns is slightly lower than desired.
--
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
[jira] [Updated] (CASSANDRA-4919) StorageProxy.getRangeSlice
sometimes returns incorrect number of columns
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-4919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis updated CASSANDRA-4919:
--------------------------------------
Affects Version/s: (was: 1.1.6)
1.1.0
Fix Version/s: 1.1.8
> StorageProxy.getRangeSlice sometimes returns incorrect number of columns
> ------------------------------------------------------------------------
>
> Key: CASSANDRA-4919
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4919
> Project: Cassandra
> Issue Type: Bug
> Affects Versions: 1.1.0
> Reporter: Piotr Kołaczkowski
> Assignee: Piotr Kołaczkowski
> Fix For: 1.1.8, 1.2.0 beta 3
>
> Attachments: 0001-Fix-getRangeSlice-paging-reset-predicate-after-fetch.patch
>
>
> When deployed on a single node, number of columns is correct.
> When deployed on a cluster, total number of returned columns is slightly lower than desired.
--
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
[jira] [Commented] (CASSANDRA-4919) StorageProxy.getRangeSlice
sometimes returns incorrect number of columns
Posted by "Tyler Patterson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-4919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13504895#comment-13504895 ]
Tyler Patterson commented on CASSANDRA-4919:
--------------------------------------------
Just added wide_slice_test to putget_test.py in the dtests.
> StorageProxy.getRangeSlice sometimes returns incorrect number of columns
> ------------------------------------------------------------------------
>
> Key: CASSANDRA-4919
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4919
> Project: Cassandra
> Issue Type: Bug
> Affects Versions: 1.1.6
> Reporter: Piotr Kołaczkowski
> Assignee: Piotr Kołaczkowski
> Fix For: 1.1.7, 1.2.0 rc1
>
> Attachments: 0001-Fix-getRangeSlice-paging-reset-predicate-after-fetch.patch
>
>
> When deployed on a single node, number of columns is correct.
> When deployed on a cluster, total number of returned columns is slightly lower than desired.
--
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
[jira] [Commented] (CASSANDRA-4919) StorageProxy.getRangeSlice
sometimes returns incorrect number of columns
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-4919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13491568#comment-13491568 ]
Jonathan Ellis commented on CASSANDRA-4919:
-------------------------------------------
Is there a dtest for this?
> StorageProxy.getRangeSlice sometimes returns incorrect number of columns
> ------------------------------------------------------------------------
>
> Key: CASSANDRA-4919
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4919
> Project: Cassandra
> Issue Type: Bug
> Affects Versions: 1.1.6
> Reporter: Piotr Kołaczkowski
> Assignee: Piotr Kołaczkowski
> Attachments: 0001-Fix-getRangeSlice-paging-reset-predicate-after-fetch.patch
>
>
> When deployed on a single node, number of columns is correct.
> When deployed on a cluster, total number of returned columns is slightly lower than desired.
--
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
[jira] [Commented] (CASSANDRA-4919) StorageProxy.getRangeSlice
sometimes returns incorrect number of columns
Posted by "Sylvain Lebresne (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-4919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13500923#comment-13500923 ]
Sylvain Lebresne commented on CASSANDRA-4919:
---------------------------------------------
I note for the testing part that this only concern getRangeSlice with the isPaging option (i.e. for thrift, get_paged_slice) and that currently CQL never calls that so this is not reproducible with CQL. We may end up using the isPaging thing in CQL with CASSANDRA-4851 however.
> StorageProxy.getRangeSlice sometimes returns incorrect number of columns
> ------------------------------------------------------------------------
>
> Key: CASSANDRA-4919
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4919
> Project: Cassandra
> Issue Type: Bug
> Affects Versions: 1.1.6
> Reporter: Piotr Kołaczkowski
> Assignee: Piotr Kołaczkowski
> Fix For: 1.1.7, 1.2.0 rc1
>
> Attachments: 0001-Fix-getRangeSlice-paging-reset-predicate-after-fetch.patch
>
>
> When deployed on a single node, number of columns is correct.
> When deployed on a cluster, total number of returned columns is slightly lower than desired.
--
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
[jira] [Updated] (CASSANDRA-4919) StorageProxy.getRangeSlice
sometimes returns incorrect number of columns
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-4919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis updated CASSANDRA-4919:
--------------------------------------
Reviewer: jbellis
> StorageProxy.getRangeSlice sometimes returns incorrect number of columns
> ------------------------------------------------------------------------
>
> Key: CASSANDRA-4919
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4919
> Project: Cassandra
> Issue Type: Bug
> Affects Versions: 1.1.6
> Reporter: Piotr Kołaczkowski
> Assignee: Piotr Kołaczkowski
> Fix For: 1.1.7, 1.2.0
>
> Attachments: 0001-Fix-getRangeSlice-paging-reset-predicate-after-fetch.patch
>
>
> When deployed on a single node, number of columns is correct.
> When deployed on a cluster, total number of returned columns is slightly lower than desired.
--
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
[jira] [Commented] (CASSANDRA-4919) StorageProxy.getRangeSlice
sometimes returns incorrect number of columns
Posted by "Brandon Williams (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-4919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13491614#comment-13491614 ]
Brandon Williams commented on CASSANDRA-4919:
---------------------------------------------
There's a wide row test and a range slice test, but not a combination of the two.
> StorageProxy.getRangeSlice sometimes returns incorrect number of columns
> ------------------------------------------------------------------------
>
> Key: CASSANDRA-4919
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4919
> Project: Cassandra
> Issue Type: Bug
> Affects Versions: 1.1.6
> Reporter: Piotr Kołaczkowski
> Assignee: Piotr Kołaczkowski
> Attachments: 0001-Fix-getRangeSlice-paging-reset-predicate-after-fetch.patch
>
>
> When deployed on a single node, number of columns is correct.
> When deployed on a cluster, total number of returned columns is slightly lower than desired.
--
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