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 2011/05/02 15:59:03 UTC
[jira] [Created] (CASSANDRA-2591) IN doesn't work with column
indexes
IN doesn't work with column indexes
-----------------------------------
Key: CASSANDRA-2591
URL: https://issues.apache.org/jira/browse/CASSANDRA-2591
Project: Cassandra
Issue Type: Bug
Components: API
Affects Versions: 0.8.1
Reporter: Jonathan Ellis
Assignee: Pavel Yaskevich
Fix For: 0.8.1
Note that we'll need to do a merge on the coordinator, because the contract is that results are returned in key order.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-2591) IN doesn't work with column
indexes
Posted by "Pavel Yaskevich (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-2591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pavel Yaskevich updated CASSANDRA-2591:
---------------------------------------
Attachment: CASSANDRA-2591.patch
work branch: cassandra-0.8, the latest commit 77b7ab228ea9207bd20311d04995d45e2592ce88
> IN doesn't work with column indexes
> -----------------------------------
>
> Key: CASSANDRA-2591
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2591
> Project: Cassandra
> Issue Type: Bug
> Components: API
> Affects Versions: 0.8.1
> Reporter: Jonathan Ellis
> Assignee: Pavel Yaskevich
> Fix For: 0.8.1
>
> Attachments: CASSANDRA-2591.patch
>
>
> Note that we'll need to do a merge on the coordinator, because the contract is that results are returned in key order.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Issue Comment Edited] (CASSANDRA-2591) IN doesn't work with
column indexes
Posted by "Pavel Yaskevich (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-2591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13045773#comment-13045773 ]
Pavel Yaskevich edited comment on CASSANDRA-2591 at 6/8/11 4:46 AM:
--------------------------------------------------------------------
I concur with you, we should close it with "Won't Fix" because performance of this query can give users negative impression.
was (Author: xedin):
I concur with ypu we should close it with "Won't Fix" because performance CSN give users negative impressions.
> IN doesn't work with column indexes
> -----------------------------------
>
> Key: CASSANDRA-2591
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2591
> Project: Cassandra
> Issue Type: Bug
> Components: API
> Affects Versions: 0.8.1
> Reporter: Jonathan Ellis
> Assignee: Pavel Yaskevich
> Fix For: 0.8.1
>
> Attachments: CASSANDRA-2591.patch
>
>
> Note that we'll need to do a merge on the coordinator, because the contract is that results are returned in key order.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-2591) IN doesn't work with column
indexes
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-2591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13045764#comment-13045764 ]
Jonathan Ellis commented on CASSANDRA-2591:
-------------------------------------------
Hmm. I think this is more complicated than I thought at first.
What if we ask for "columnX IN (1, 2, 3, 4, 5) AND columnY IN (6, 7, 8, 9, 10)" for instance? That's 25 queries to combine! ({x=1,y=6}, {x=1, y=7}, ...)
Starting to think we should close as wontfix. Thoughts?
> IN doesn't work with column indexes
> -----------------------------------
>
> Key: CASSANDRA-2591
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2591
> Project: Cassandra
> Issue Type: Bug
> Components: API
> Affects Versions: 0.8.1
> Reporter: Jonathan Ellis
> Assignee: Pavel Yaskevich
> Fix For: 0.8.1
>
> Attachments: CASSANDRA-2591.patch
>
>
> Note that we'll need to do a merge on the coordinator, because the contract is that results are returned in key order.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-2591) IN doesn't work with column
indexes
Posted by "Pavel Yaskevich (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-2591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13045773#comment-13045773 ]
Pavel Yaskevich commented on CASSANDRA-2591:
--------------------------------------------
I concur with ypu we should close it with "Won't Fix" because performance CSN give users negative impressions.
> IN doesn't work with column indexes
> -----------------------------------
>
> Key: CASSANDRA-2591
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2591
> Project: Cassandra
> Issue Type: Bug
> Components: API
> Affects Versions: 0.8.1
> Reporter: Jonathan Ellis
> Assignee: Pavel Yaskevich
> Fix For: 0.8.1
>
> Attachments: CASSANDRA-2591.patch
>
>
> Note that we'll need to do a merge on the coordinator, because the contract is that results are returned in key order.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira