You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Kirk True (JIRA)" <ji...@apache.org> on 2015/05/05 01:56:07 UTC
[jira] [Commented] (CASSANDRA-4938) CREATE INDEX can block for
creation now that schema changes may be concurrent
[ https://issues.apache.org/jira/browse/CASSANDRA-4938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14527583#comment-14527583 ]
Kirk True commented on CASSANDRA-4938:
--------------------------------------
Any updates on this?
> 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.x
>
>
> 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)