cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kirk True (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (CASSANDRA-4938) CREATE INDEX can block for creation now that schema changes may be concurrent
Date Sat, 13 Sep 2014 17:17:33 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-4938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Kirk True reassigned CASSANDRA-4938:
------------------------------------

    Assignee: Kirk True

> CREATE INDEX can block for creation now that schema changes may be concurrent
> -----------------------------------------------------------------------------
>
>                 Key: CASSANDRA-4938
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4938
>             Project: Cassandra
>          Issue Type: Wish
>            Reporter: Krzysztof Cieslinski Cognitum
>            Assignee: Kirk True
>            Priority: Minor
>              Labels: lhf
>             Fix For: 3.0
>
>
> Response from CREATE INDEX command comes faster than the creation of secondary index.
So below code:
> {code:xml}
> CREATE INDEX ON tab(name);
> SELECT * FROM tab WHERE name = 'Chris';
> {code}
> doesn't return any rows(of course, in column family "tab", there are some records with
"name" value = 'Chris'..) and any errors ( i would expect something like ??"Bad Request: No
indexed columns present in by-columns clause with Equal operator"??) 
> Inputing some timeout between those two commands resolves the problem, so:
> {code:xml}
> CREATE INDEX ON tab(name);
> Sleep(timeout); // for column family with 2000 rows the timeout had to be set for ~1
second 
> SELECT * FROM tab WHERE name = 'Chris';
> {code}
> will return all rows with values as specified.
> I'm using single node cluster.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message