[
https://issues.apache.org/jira/browse/CASSANDRA-5123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13555187#comment-13555187
]
Sylvain Lebresne commented on CASSANDRA-5123:
---------------------------------------------
bq. Why is it unsafe to share filter in SelectStatement for NQF?
It's not. Figured the cloneShallow was probably negligible enough to ignore in
that case since it yield simpler code. That being said, since NQF is immutable
(at least as far as cloning shallow is concerned), I suppose making its
cloneShallow just return {{this}} is a valid option.
> Multiget Supercolumns Sometimes Missing Results
> -----------------------------------------------
>
> Key: CASSANDRA-5123
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5123
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 2.0
> Reporter: Tyler Hobbs
> Assignee: Sylvain Lebresne
> Priority: Minor
> Fix For: 2.0
>
> Attachments: 5123.txt
>
>
> Starting approximately with commit c2812f3 (the January 3rd nightly build by
> DataStax Jenkins, #669), a few of the pycassa unit tests related to
> multigetting a particular supercolumn started failing periodically. The
> nightly build is against Cassandra trunk.
> You can reproduce with the pycassa unit tests fairly easily:
> {noformat}
> nosetests
> tests/test_columnfamily.py:TestSuperColumnFamily.test_multiget_supercolumn
> {noformat}
> It should fail within a few runs.
> It looks like one of the requested keys isn't being returned at all.
--
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
