You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Krzysztof Cieslinski Cognitum (JIRA)" <ji...@apache.org> on 2012/11/09 14:20:12 UTC

[jira] [Created] (CASSANDRA-4938) Response from CREATE INDEX command comes faster than the creation of secondary index.

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

[jira] [Updated] (CASSANDRA-4938) CREATE INDEX can block for creation now that schema changes may be concurrent

Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CASSANDRA-4938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Ellis updated CASSANDRA-4938:
--------------------------------------

             Priority: Minor  (was: Major)
    Affects Version/s:     (was: 1.2.0 beta 1)
        Fix Version/s: 1.3
           Issue Type: Wish  (was: Bug)
              Summary: CREATE INDEX can block for creation now that schema changes may be concurrent  (was: Response from CREATE INDEX command comes faster than the creation of secondary index.)
    
> 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
>            Priority: Minor
>             Fix For: 1.3
>
>
> 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