[ https://issues.apache.org/jira/browse/CASSANDRA-10216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14745261#comment-14745261 ]
Alexandre Dutra commented on CASSANDRA-10216: --------------------------------------------- [~beobal] A compatible java driver version can be found [here|https://github.com/datastax/java-driver/pull/452]. We have a small problem with case-sensitive columns: suppose one creates an index on {{values("MixedCaseColumn")}}; the target column would then contain {{values(MixedCaseColumn)}} - note that the column identifier is unquoted; since the driver is not parsing this string, it is unable to recreate the original CREATE INDEX statement. > Remove target type from internal index metadata > ----------------------------------------------- > > Key: CASSANDRA-10216 > URL: https://issues.apache.org/jira/browse/CASSANDRA-10216 > Project: Cassandra > Issue Type: Improvement > Reporter: Sam Tunnicliffe > Assignee: Sam Tunnicliffe > Labels: client-impacting > Fix For: 3.0.0 rc1 > > > As part of CASSANDRA-6716 & in anticipation of CASSANDRA-10124, a distinction > was introduced between secondary indexes which target a fixed set of 1 or > more columns in the base data, and those which are agnostic to the structure > of the underlying rows. This distinction is manifested in > {{IndexMetadata.targetType}} and {{system_schema.indexes}}, in the > {{target_type}} column. It could be argued that this distinction complicates > the codebase without providing any tangible benefit, given that the target > type is not actually used anywhere. > It's only the impact on {{system_schema.indexes}} that makes puts this on the > critical path for 3.0, any code changes are just implementation details. -- This message was sent by Atlassian JIRA (v6.3.4#6332)