You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Roland Gude (JIRA)" <ji...@apache.org> on 2012/06/12 17:07:42 UTC
[jira] [Created] (CASSANDRA-4332) IndexRangeSliceQuery results
contain IndexColumn even though it is not included in SliceRange
Roland Gude created CASSANDRA-4332:
--------------------------------------
Summary: IndexRangeSliceQuery results contain IndexColumn even though it is not included in SliceRange
Key: CASSANDRA-4332
URL: https://issues.apache.org/jira/browse/CASSANDRA-4332
Project: Cassandra
Issue Type: Bug
Affects Versions: 1.1.1
Reporter: Roland Gude
This is the magical reappearance of CASSANDRA-2964
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-4332) IndexRangeSliceQuery results
contain IndexColumn even though it is not included in SliceRange
Posted by "Roland Gude (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-4332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13396887#comment-13396887 ]
Roland Gude commented on CASSANDRA-4332:
----------------------------------------
excerpt from a debug log
DEBUG [Thrift:12] 2012-06-19 17:57:28,531 StorageProxy.java (line 891) reading RangeSliceCommand{keyspace='Eventstore', column_family='EventsByItem', super_column=null, predicate=SlicePredicate(slice_range:S
liceRange(start:80 01 00 01 00 00 00 12 67 65 74 5F 69 6E 64 65 78 65 64 5F 73 6C 69 63 65 73 00 00 00 06 0C 00 01 0B 00 03 00 00 00 0C 45 76 65 6E 74 73 42 79 49 74 65 6D 00 0C 00 02 0F 00 01 0C 00 00 00 01
0B 00 01 00 00 00 10 00 00 00 03 00 00 10 00 00 00 00 00 00 00 00 00 08 00 02 00 00 00 00 0B 00 03 00 00 00 08 31 30 30 32 38 21 21 32 00 0B 00 02 00 00 00 17 31 30 30 32 38 21 21 32 21 21 31..., finish:80
01 00 01 00 00 00 12 67 65 74 5F 69 6E 64 65 78 65 64 5F 73 6C 69 63 65 73 00 00 00 06 0C 00 01 0B 00 03 00 00 00 0C 45 76 65 6E 74 73 42 79 49 74 65 6D 00 0C 00 02 0F 00 01 0C 00 00 00 01 0B 00 01 00 00 00
10 00 00 00 03 00 00 10 00 00 00 00 00 00 00 00 00 08 00 02 00 00 00 00 0B 00 03 00 00 00 08 31 30 30 32 38 21 21 32 00 0B 00 02 00 00 00 17 31 30 30 32 38 21 21 32 21 21 31..., reversed:true, count:1000)),
range=[DecoratedKey(167646021443590589642928446312405002082, 3130303238212132212131212131303630333931303030),min(-1)], row_filter =[IndexExpression(column_name:80 01 00 01 00 00 00 12 67 65 74 5F 69 6E 64 65
78 65 64 5F 73 6C 69 63 65 73 00 00 00 06 0C 00 01 0B 00 03 00 00 00 0C 45 76 65 6E 74 73 42 79 49 74 65 6D 00 0C 00 02 0F 00 01 0C 00 00 00 01 0B 00 01 00 00 00 10 00 00 00 03 00 00 10 00 00 00 00 00 00 00
00 00, op:EQ, value:80 01 00 01 00 00 00 12 67 65 74 5F 69 6E 64 65 78 65 64 5F 73 6C 69 63 65 73 00 00 00 06 0C 00 01 0B 00 03 00 00 00 0C 45 76 65 6E 74 73 42 79 49 74 65 6D 00 0C 00 02 0F 00 01 0C 00 00
00 01 0B 00 01 00 00 00 10 00 00 00 03 00 00 10 00 00 00 00 00 00 00 00 00 08 00 02 00 00 00 00 0B 00 03 00 00 00 08 31 30 30 32 38 21 21 32)], maxResults=101, maxIsColumns=false} from /10.227.206.178
DEBUG [ReadStage:390] 2012-06-19 17:57:28,533 KeysSearcher.java (line 99) Primary scan clause is 00000003-0000-1000-0000-000000000000
DEBUG [ReadStage:390] 2012-06-19 17:57:28,533 ColumnFamilyStore.java (line 1425) Filtering org.apache.cassandra.db.index.keys.KeysSearcher$1@44f36e1 for rows matching org.apache.cassandra.db.filter.ExtendedF
ilter$FilterWithClauses@6c9beffc
DEBUG [ReadStage:390] 2012-06-19 17:57:28,533 KeysSearcher.java (line 135) Scanning index 'EventsByItem.00000003-0000-1000-0000-000000000000 EQ 3130303238212132' starting with 3130303238212132212131212131303
630333931303030
DEBUG [ReadStage:390] 2012-06-19 17:57:28,534 CollationController.java (line 226) collectAllData
DEBUG [ReadStage:390] 2012-06-19 17:57:28,538 SliceQueryFilter.java (line 123) collecting 0 of 101: 3130303238212132212131212131303630333931303030:false:0@1316005644991011
DEBUG [ReadStage:390] 2012-06-19 17:57:28,539 SliceQueryFilter.java (line 123) collecting 1 of 101: 3130303238212132212131212131303337323731303033:false:0@1316005647056003
DEBUG [ReadStage:390] 2012-06-19 17:57:28,539 SliceQueryFilter.java (line 123) collecting 2 of 101: 3130303238212132212131212131313133363332303037:false:0@1316005647057002
DEBUG [ReadStage:390] 2012-06-19 17:57:28,539 SliceQueryFilter.java (line 123) collecting 3 of 101: 3130303238212132212131212131313136383732303030:false:0@1316005647058003
DEBUG [ReadStage:390] 2012-06-19 17:57:28,539 SliceQueryFilter.java (line 123) collecting 4 of 101: 3130303238212132212131212131303639313336303030:false:0@1316005647059001
DEBUG [ReadStage:390] 2012-06-19 17:57:28,539 SliceQueryFilter.java (line 123) collecting 5 of 101: 3130303238212132212131212131303237353539303032:false:0@1316005647115003
...
...
DEBUG [ReadStage:390] 2012-06-19 17:57:28,551 KeysSearcher.java (line 194) Returning index hit for DecoratedKey(167646021443590589642928446312405002082, 3130303238212132212131212131303630333931303030)
DEBUG [ReadStage:390] 2012-06-19 17:57:28,551 CollationController.java (line 226) collectAllData
DEBUG [ReadStage:390] 2012-06-19 17:57:28,553 ExtendedFilter.java (line 228) adding extraFilter to cover additional expressions
DEBUG [ReadStage:390] 2012-06-19 17:57:28,553 CollationController.java (line 77) collectTimeOrderedData
DEBUG [ReadStage:390] 2012-06-19 17:57:28,554 ColumnFamilyStore.java (line 1449) ColumnFamily(EventsByItem [00000003-0000-1000-0000-000000000000:false:8@1316005644991011,]) satisfies all filter expressions
DEBUG [ReadStage:390] 2012-06-19 17:57:28,554 KeysSearcher.java (line 194) Returning index hit for DecoratedKey(167651587728849940211857023761050559342, 3130303238212132212131212131303337323731303033)
DEBUG [ReadStage:390] 2012-06-19 17:57:28,554 CollationController.java (line 226) collectAllData
DEBUG [ReadStage:390] 2012-06-19 17:57:28,555 ExtendedFilter.java (line 228) adding extraFilter to cover additional expressions
DEBUG [ReadStage:390] 2012-06-19 17:57:28,555 CollationController.java (line 77) collectTimeOrderedData
DEBUG [ReadStage:390] 2012-06-19 17:57:28,556 ColumnFamilyStore.java (line 1449) ColumnFamily(EventsByItem [00000003-0000-1000-0000-000000000000:false:8@1316005647056003,]) satisfies all filter expressions
DEBUG [ReadStage:390] 2012-06-19 17:57:28,556 KeysSearcher.java (line 194) Returning index hit for DecoratedKey(167653432788587316103047344162913572390, 3130303238212132212131212131313133363332303037)
DEBUG [ReadStage:390] 2012-06-19 17:57:28,556 CollationController.java (line 226) collectAllData
DEBUG [ReadStage:390] 2012-06-19 17:57:28,557 ExtendedFilter.java (line 228) adding extraFilter to cover additional expressions
DEBUG [ReadStage:390] 2012-06-19 17:57:28,557 CollationController.java (line 77) collectTimeOrderedData
DEBUG [ReadStage:390] 2012-06-19 17:57:28,559 ColumnFamilyStore.java (line 1449) ColumnFamily(EventsByItem [00000003-0000-1000-0000-000000000000:false:8@1316005647057002,]) satisfies all filter expressions
DEBUG [ReadStage:390] 2012-06-19 17:57:28,559 KeysSearcher.java (line 194) Returning index hit for DecoratedKey(167665727967911988689787413962915043827, 3130303238212132212131212131313136383732303030)
> IndexRangeSliceQuery results contain IndexColumn even though it is not included in SliceRange
> ---------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-4332
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4332
> Project: Cassandra
> Issue Type: Bug
> Affects Versions: 1.1.1
> Reporter: Roland Gude
> Attachments: system.log, system.log
>
>
> This is the magical reappearance of CASSANDRA-2964
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-4332) IndexRangeSliceQuery results
contain IndexColumn even though it is not included in SliceRange
Posted by "Roland Gude (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-4332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Roland Gude updated CASSANDRA-4332:
-----------------------------------
Attachment: system.log
node with server side exceptions
> IndexRangeSliceQuery results contain IndexColumn even though it is not included in SliceRange
> ---------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-4332
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4332
> Project: Cassandra
> Issue Type: Bug
> Affects Versions: 1.1.1
> Reporter: Roland Gude
> Attachments: system.log, system.log
>
>
> This is the magical reappearance of CASSANDRA-2964
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-4332) IndexRangeSliceQuery results
contain IndexColumn even though it is not included in SliceRange
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-4332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13398612#comment-13398612 ]
Jonathan Ellis commented on CASSANDRA-4332:
-------------------------------------------
Can you reproduce on a single-node cluster, or does it need multiple nodes to show problems?
> IndexRangeSliceQuery results contain IndexColumn even though it is not included in SliceRange
> ---------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-4332
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4332
> Project: Cassandra
> Issue Type: Bug
> Affects Versions: 1.1.1
> Reporter: Roland Gude
> Attachments: system.log, system.log, system.log
>
>
> This is the magical reappearance of CASSANDRA-2964
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-4332) IndexRangeSliceQuery results
contain IndexColumn even though it is not included in SliceRange
Posted by "Roland Gude (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-4332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13397513#comment-13397513 ]
Roland Gude commented on CASSANDRA-4332:
----------------------------------------
some more info on this:
IndexQueries with ColumnRange(somestart, someend) apparently return no TimeUUIDs later then mid december 2011 and they include the indexcolumn even though it is not in the ColumnRange.
RangeQueries with the exact same ColumnRange as above return the correct data.
is this maybe related to Cassandra-1600?
> IndexRangeSliceQuery results contain IndexColumn even though it is not included in SliceRange
> ---------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-4332
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4332
> Project: Cassandra
> Issue Type: Bug
> Affects Versions: 1.1.1
> Reporter: Roland Gude
> Attachments: system.log, system.log, system.log
>
>
> This is the magical reappearance of CASSANDRA-2964
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-4332) IndexRangeSliceQuery results
contain IndexColumn even though it is not included in SliceRange
Posted by "Roland Gude (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-4332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13293716#comment-13293716 ]
Roland Gude commented on CASSANDRA-4332:
----------------------------------------
i am not entirely sure i identified the issue correct. even though i saw wrong results returned from the cluster it was with an old client version (hector 0.7) but with newer hector i cannot see the wrong results. i do get Exceptions on some nodes in the cluster however ( see debug logs - attached complete and an exceprt in teh comment)
---------
DEBUG [Thrift:8] 2012-06-12 17:53:48,807 KeysSearcher.java (line 135) Scanning index 'EventsByItem.00000003-0000-1000-0000-000000000000 EQ 343631212132' starting with
DEBUG [Thrift:8] 2012-06-12 17:53:48,807 CollationController.java (line 226) collectAllData
DEBUG [Thrift:8] 2012-06-12 17:53:48,807 KeysSearcher.java (line 145) fetched null
DEBUG [Thrift:8] 2012-06-12 17:53:48,808 KeysSearcher.java (line 148) no data, all done
DEBUG [Thrift:8] 2012-06-12 17:53:49,207 CustomTThreadPoolServer.java (line 196) Thrift transport error occurred during processing of message.
org.apache.thrift.transport.TTransportException: java.net.SocketException: Connection reset
at org.apache.thrift.transport.TIOStreamTransport.read(TIOStreamTransport.java:129)
at org.apache.thrift.transport.TTransport.readAll(TTransport.java:84)
at org.apache.thrift.transport.TFramedTransport.readFrame(TFramedTransport.java:129)
at org.apache.thrift.transport.TFramedTransport.read(TFramedTransport.java:101)
at org.apache.thrift.transport.TTransport.readAll(TTransport.java:84)
at org.apache.thrift.protocol.TBinaryProtocol.readAll(TBinaryProtocol.java:378)
at org.apache.thrift.protocol.TBinaryProtocol.readI32(TBinaryProtocol.java:297)
at org.apache.thrift.protocol.TBinaryProtocol.readMessageBegin(TBinaryProtocol.java:204)
at org.apache.thrift.TBaseProcessor.process(TBaseProcessor.java:22)
at org.apache.cassandra.thrift.CustomTThreadPoolServer$WorkerProcess.run(CustomTThreadPoolServer.java:186)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
Caused by: java.net.SocketException: Connection reset
at java.net.SocketInputStream.read(SocketInputStream.java:168)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
at java.io.BufferedInputStream.read1(BufferedInputStream.java:258)
at java.io.BufferedInputStream.read(BufferedInputStream.java:317)
at org.apache.thrift.transport.TIOStreamTransport.read(TIOStreamTransport.java:127)
... 12 more
DEBUG [Thrift:8] 2012-06-12 17:53:49,208 ClientState.java (line 130) logged out: #<User allow_all groups=[]>
DEBUG [ScheduledTasks:1] 2012-06-12 17:53:58,892 LoadBroadcaster.java (line 86) Disseminating load info ...
> IndexRangeSliceQuery results contain IndexColumn even though it is not included in SliceRange
> ---------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-4332
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4332
> Project: Cassandra
> Issue Type: Bug
> Affects Versions: 1.1.1
> Reporter: Roland Gude
>
> This is the magical reappearance of CASSANDRA-2964
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-4332) IndexRangeSliceQuery results
contain IndexColumn even though it is not included in SliceRange
Posted by "Roland Gude (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-4332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Roland Gude updated CASSANDRA-4332:
-----------------------------------
Attachment: system.log
node where all is fine
> IndexRangeSliceQuery results contain IndexColumn even though it is not included in SliceRange
> ---------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-4332
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4332
> Project: Cassandra
> Issue Type: Bug
> Affects Versions: 1.1.1
> Reporter: Roland Gude
> Attachments: system.log
>
>
> This is the magical reappearance of CASSANDRA-2964
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-4332) IndexRangeSliceQuery results
contain IndexColumn even though it is not included in SliceRange
Posted by "Roland Gude (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-4332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13397516#comment-13397516 ]
Roland Gude commented on CASSANDRA-4332:
----------------------------------------
to clarify the comment above:
when i said they do not return anything later then mid december then i meant that they do not do that even though they should do it, as the columnrange includes those timeuuids and they are in the dataset.
> IndexRangeSliceQuery results contain IndexColumn even though it is not included in SliceRange
> ---------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-4332
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4332
> Project: Cassandra
> Issue Type: Bug
> Affects Versions: 1.1.1
> Reporter: Roland Gude
> Attachments: system.log, system.log, system.log
>
>
> This is the magical reappearance of CASSANDRA-2964
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-4332) IndexRangeSliceQuery results
contain IndexColumn even though it is not included in SliceRange
Posted by "Roland Gude (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-4332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13294244#comment-13294244 ]
Roland Gude commented on CASSANDRA-4332:
----------------------------------------
i think i understand the issue now:
It is dependant on Consistency Level/Replication and our usage of index queries (which i guess several other people are using similar)
What we do is a index query and paging over the results (i.e. request 100 rows, if we get 100 rows - fetch next 100 if we get less, stop)
Using consistency level one apparently there is a situation where the node which started the query cannot satisfy the number of requested rows and simply returns those he has - which is less then the expected number of rows. so paging thinks there is nothing more and just stops.
Using consistency level ALL (or Quorum) the request seems to reach the node which has the replica as well. That node now adds to the results the local indexed rows starting from the given token. The results are merged and returned. now - if first node cannot satisfy the number of requested rows - the result will contain items from a node with another token range and paging can continue on that other node.
If this is the case, this comes with several caveats.
In order to get consistent results from a paging index query, it is required to either - page over all tokensranges from the cluster manually
or use consistency level ALL and make sure that replication layout gives you adjacent token ranges (i.e. SimpleStrategy). Any other strategy might mess up results, I guess.
does this sound at least half way reasonable?
> IndexRangeSliceQuery results contain IndexColumn even though it is not included in SliceRange
> ---------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-4332
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4332
> Project: Cassandra
> Issue Type: Bug
> Affects Versions: 1.1.1
> Reporter: Roland Gude
> Attachments: system.log, system.log
>
>
> This is the magical reappearance of CASSANDRA-2964
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-4332) IndexRangeSliceQuery results
contain IndexColumn even though it is not included in SliceRange
Posted by "Roland Gude (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-4332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13294209#comment-13294209 ]
Roland Gude commented on CASSANDRA-4332:
----------------------------------------
i will check with other clients.
but isn't it strange that client does not report failures back and that it works on one node but not on another in the same cluster?
anyway i will investigate further and maybe this turns out to be a client thing...
> IndexRangeSliceQuery results contain IndexColumn even though it is not included in SliceRange
> ---------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-4332
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4332
> Project: Cassandra
> Issue Type: Bug
> Affects Versions: 1.1.1
> Reporter: Roland Gude
> Attachments: system.log, system.log
>
>
> This is the magical reappearance of CASSANDRA-2964
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-4332) IndexRangeSliceQuery results
contain IndexColumn even though it is not included in SliceRange
Posted by "Roland Gude (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-4332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Roland Gude updated CASSANDRA-4332:
-----------------------------------
Attachment: system.log
newest system log
with wrong results
> IndexRangeSliceQuery results contain IndexColumn even though it is not included in SliceRange
> ---------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-4332
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4332
> Project: Cassandra
> Issue Type: Bug
> Affects Versions: 1.1.1
> Reporter: Roland Gude
> Attachments: system.log, system.log, system.log
>
>
> This is the magical reappearance of CASSANDRA-2964
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-4332) IndexRangeSliceQuery results
contain IndexColumn even though it is not included in SliceRange
Posted by "Roland Gude (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-4332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13396878#comment-13396878 ]
Roland Gude commented on CASSANDRA-4332:
----------------------------------------
I started a new cluster and imported my dataset again.
i tried this with several clients now (hector 0.7 hector 1.1 and astyanax 1.0.3)
with all clients results on index queries contain the index column (on which the equal clause was set). As far as i can tell, they do not contain the requestet ColumnSlice at all.
I will create more tests and debug logs.
> IndexRangeSliceQuery results contain IndexColumn even though it is not included in SliceRange
> ---------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-4332
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4332
> Project: Cassandra
> Issue Type: Bug
> Affects Versions: 1.1.1
> Reporter: Roland Gude
> Attachments: system.log, system.log
>
>
> This is the magical reappearance of CASSANDRA-2964
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-4332) IndexRangeSliceQuery results
contain IndexColumn even though it is not included in SliceRange
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-4332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13293789#comment-13293789 ]
Jonathan Ellis commented on CASSANDRA-4332:
-------------------------------------------
Those just look like "client disconnected unexpectedly" exceptions.
> IndexRangeSliceQuery results contain IndexColumn even though it is not included in SliceRange
> ---------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-4332
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4332
> Project: Cassandra
> Issue Type: Bug
> Affects Versions: 1.1.1
> Reporter: Roland Gude
> Attachments: system.log, system.log
>
>
> This is the magical reappearance of CASSANDRA-2964
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira