[
https://issues.apache.org/jira/browse/CASSANDRA-6477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14363744#comment-14363744
]
Carl Yeksigian commented on CASSANDRA-6477:
-------------------------------------------
Looking at the changes I made, it is currently only disallowing
dropping/altering/renaming the target column.
Here's a list of the actions and how the GI could handle them:
- DROP
- If the target column, either error and say to drop GI first, or drop GI
with the column drop
- If included, GI drops that column
- ALTER should be handled the same way for GI as the base table
- RENAME of the target is allowed, since we are storing the CF ID separately
and don't have the same problem as 2i in CASSANDRA-5705; everything else is
handled if it would be handled under the normal RENAME
- ADD a column to a CF with a GI {{INCLUDE (\*)}} should add column as well
- WITH should change the parameters of GI CF as well
> Global indexes
> --------------
>
> Key: CASSANDRA-6477
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6477
> Project: Cassandra
> Issue Type: New Feature
> Components: API, Core
> Reporter: Jonathan Ellis
> Assignee: Carl Yeksigian
> Labels: cql
> Fix For: 3.0
>
>
> Local indexes are suitable for low-cardinality data, where spreading the
> index across the cluster is a Good Thing. However, for high-cardinality
> data, local indexes require querying most nodes in the cluster even if only a
> handful of rows is returned.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
