[
https://issues.apache.org/jira/browse/CASSANDRA-8156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14201896#comment-14201896
]
Denis Angilella commented on CASSANDRA-8156:
--------------------------------------------
[~slebresne]: My intention when creating this ticket was not necessarily to
support indexes on primary key columns for compact tables, but to have a not
misleading behavior. So I agree that validation should be fixed instead.
+1 for not adding this feature to legacy tables.
> Fix validation of indexes on composite column components of COMPACT tables
> --------------------------------------------------------------------------
>
> Key: CASSANDRA-8156
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8156
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Reporter: Denis Angilella
> Assignee: Sylvain Lebresne
> Priority: Trivial
> Fix For: 2.0.12
>
> Attachments: 8156.txt
>
>
> CASSANDRA-5125 added support of indexes on composite column components for
> *non-compact* tables (see CASSANDRA-5125 comments for additional information).
> This is a follow up for *compact* tables.
> Using compact tables it is possible to CREATE INDEX on composite primary key
> columns, but queries returns no results for the tests below.
> {code:sql}
> CREATE TABLE users2 (
> userID uuid,
> fname text,
> zip int,
> state text,
> PRIMARY KEY ((userID, fname))
> ) WITH COMPACT STORAGE;
> CREATE INDEX ON users2 (userID);
> CREATE INDEX ON users2 (fname);
> INSERT INTO users2 (userID, fname, zip, state) VALUES
> (b3e3bc33-b237-4b55-9337-3d41de9a5649, 'John', 10007, 'NY');
> -- the following queries returns 0 rows, instead of 1 expected
> SELECT * FROM users2 WHERE fname='John';
> SELECT * FROM users2 WHERE userid=b3e3bc33-b237-4b55-9337-3d41de9a5649;
> SELECT * FROM users2 WHERE userid=b3e3bc33-b237-4b55-9337-3d41de9a5649 AND
> fname='John';
> -- dropping 2ndary indexes restore normal behavior
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
