Hi,
I've noticed that our datamodel has many unnecessary secondary indexes. Are
there a recommended procedure to drop a secondary index on a very large table?
Is there any sort of repair/cleanup that should be done after calling the DROP
command?
Thanks,
Parag
https://issues.apache.org/jira/browse/CASSANDRA-3054
On Wed, Aug 17, 2011 at 7:13 PM, aaron morton wrote:
> ooo, didn't know there was a drop index statement.
>
> I got the same result, the Antlr grammar seems to say it's a valid
> identifier (not that I have much Antlr foo)…
>
>
> Identifier
>
ooo, didn't know there was a drop index statement.
I got the same result, the Antlr grammar seems to say it's a valid identifier
(not that I have much Antlr foo)…
Identifier
: (Letter | Alnum) (Alnum | '_' | '-' )*
fragment
Letter
: 'a'..'z'
| 'A'..'Z'
;
fragment
Digit
:
Thanks, Aaron! In terms of dropping stuff from the CLI, I tried to re-drop
the remaining built column index and get the following error message. I
wonder if there's some sort of parser bug related to numeric vs alpha
tokens. The column name below is col2 from the show keyspace dump earlier
in th
> I think I've dropped all the indexes on a CF, but I see traces of them in the
> CLI output of show keyspaces. I see a few validators left behind, and one
> "built index". (output below)
What process did you use to drop the indexes ? You need to use update column
family and not include the c
I think I've dropped all the indexes on a CF, but I see traces of them in
the CLI output of show keyspaces. I see a few validators left behind, and
one "built index". (output below)
1. Is there a better way to check schema for indexes?
2. I can't drop the "built" one so I assume they're all gone
