[ https://issues.apache.org/jira/browse/CASSANDRA-7771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14707211#comment-14707211 ]
Sam Tunnicliffe commented on CASSANDRA-7771: -------------------------------------------- bq. don't ever allow creating the "same" index twice on the same column "near-duplicate" check added in [da25991|https://github.com/beobal/cassandra/commit/da25991bd1b17ec2e53c2990eba91e3b5a6d03bf] > Allow multiple 2ndary index on the same column > ---------------------------------------------- > > Key: CASSANDRA-7771 > URL: https://issues.apache.org/jira/browse/CASSANDRA-7771 > Project: Cassandra > Issue Type: New Feature > Reporter: Sylvain Lebresne > Assignee: Sam Tunnicliffe > Labels: client-impacting > Fix For: 3.0 beta 1 > > > Currently, the code assumes that we'll only have one 2ndary index per column. > This has been reasonable so far but stop being it with CASSANDRA-6382 (you > might want to index multiple fields of the same UDT column) and > CASSANDRA-7458 (you may want to have one "normal" index an multiple > functional index for the same column). So we should consider removing that > assumption in the code, which is mainly 2 places: > # in the schema: each ColumnDefinition only has infos for one index. This > part should probably be tackled in CASSANDRA-6717 so I'm marking this issue > as a follow-up of CASSANDRA-6717. > # in the 2ndary index API: this is the part I'm suggesting we fix in this > issue. -- This message was sent by Atlassian JIRA (v6.3.4#6332)