Krzysztof Cieslinski Cognitum created CASSANDRA-4938:
--------------------------------------------------------
Summary: Response from CREATE INDEX command comes faster than the
creation of secondary index.
Key: CASSANDRA-4938
URL: https://issues.apache.org/jira/browse/CASSANDRA-4938
Project: Cassandra
Issue Type: Bug
Affects Versions: 1.2.0 beta 1
Reporter: Krzysztof Cieslinski Cognitum
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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
