[
https://issues.apache.org/jira/browse/CASSANDRA-2964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13078873#comment-13078873
]
Jonathan Ellis commented on CASSANDRA-2964:
-------------------------------------------
Hi Roland,
I think the attached patch should fix the problem. If it does not, what we
need to troubleshoot is the debug logs from the data nodes, e.g., 10.234.81.208
when it the coordinator logs, "reading
org.apache.cassandra.db.IndexScanCommand@22bb5662 from /10.234.81.208".
> IndexRangeSliceQuery results include index column even though it is not in
> SliceRange
> -------------------------------------------------------------------------------------
>
> Key: CASSANDRA-2964
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2964
> Project: Cassandra
> Issue Type: Bug
> Affects Versions: 0.7.7
> Reporter: Roland Gude
> Attachments: 2964-0.7.txt, TestIndexRangeSliceQuery.java,
> cassandra.yaml
>
>
> When an IndexSlicwQuery is done the result contains the index column even
> though it was not in the slice range.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
