Russ Hatch created CASSANDRA-8154:
-------------------------------------
Summary: desc table output shows key-only index ambiguously
Key: CASSANDRA-8154
URL: https://issues.apache.org/jira/browse/CASSANDRA-8154
Project: Cassandra
Issue Type: Bug
Reporter: Russ Hatch
Priority: Minor
When creating a secondary index on a map type, for keys, the DESC TABLE output
does not create correct DDL (it omits the keys part). So if someone uses
describe to recreate a schema they could end up with a values index instead of
a keys index.
First, create a table and add an index:
{noformat}
CREATE TABLE test.foo (
id1 text,
id2 text,
categories map<text, text>,
PRIMARY KEY (id1, id2));
create index on foo(keys(categories));|
{noformat}
Now DESC TABLE and you'll see the incomplete index DDL:
{noformat}
CREATE TABLE test.foo (
id1 text,
id2 text,
categories map<text, text>,
PRIMARY KEY (id1, id2)
) WITH CLUSTERING ORDER BY (id2 ASC)
.......................snip..............................................
CREATE INDEX foo_categories_idx ON test.foo (categories);
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
