You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Sergey Nagaytsev (JIRA)" <ji...@apache.org> on 2013/12/09 11:45:07 UTC
[jira] [Updated] (CASSANDRA-6318) IN predicates on non-primary-key
columns (%s) is not yet supported
[ https://issues.apache.org/jira/browse/CASSANDRA-6318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sergey Nagaytsev updated CASSANDRA-6318:
----------------------------------------
Attachment: CASSANDRA_6318_test.cql
No, it's not fixed in 2.0.3. Here's the test file.
Will it be fixed ever, how long is the 'yet' in error message ? What is the milestone or plan ?
Now i'm on the brink of massively adding my own column families as IN()-able indexes, together with application logic.
Should i do so in the way allowing easy uprooting and rollback to future IN-able secondary indexes, or is this permanent way of affairs, and fix will be just deleting 'yet' ?
> IN predicates on non-primary-key columns (%s) is not yet supported
> ------------------------------------------------------------------
>
> Key: CASSANDRA-6318
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6318
> Project: Cassandra
> Issue Type: Bug
> Reporter: Sergey Nagaytsev
> Labels: cql3
> Attachments: CASSANDRA_6318_test.cql
>
>
> Query:
> SELECT * FROM post WHERE blog IN (1,2) AND author=3 ALLOW FILTERING -- contrived
> Error: IN predicates on non-primary-key columns (blog) is not yet supported
> Please either implement, set milestone or say will never be implemented !
> P.S. Did search, seemingly found no issue/plan related to it. Maybe CASSANDRA-6048 ?
> P.S.2 What is recommended workaround for this ? Manual index tables, what are design guidelines for them ?
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)