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/12 12:07:08 UTC
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=13846244#comment-13846244 ]
Sergey Nagaytsev commented on CASSANDRA-6318:
---------------------------------------------
OK, i have heard it, so:
1) How important is it deemed by the team ? My usage scenario is RDBMS-oriented (but happily JOIN-less) DBAL + business application, it makes IN() queries on any columns, like they are indexed integer IDs. Does the team consider this usage scenario as main or popular ? What is the mental image of C* usage in the team ? Log/sensor dump with expiry, single-task inverse index, focused social site w/ few purpose tables (user,post/picture/whatever,like/comment,tag) and few inverse indices ? How far is it from mine - take a big business app or project of it, switch from Oracle to C* in one config line, fix bugs if any ?
2) How hard is it to implement ? What are classes involved ? What is magnitude of changes - just add one loop instead of single execution, or will it take ground-up architecture overhaul ? If i comment out the exception in cassandra.cql3.statements.SelectStatement.RawStatement#prepare, what and where will break ?
> 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)