cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Evans (Commented) (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-3424) Selecting just the row_key returns nil instead of just the row_key
Date Tue, 20 Dec 2011 16:58:30 GMT


Eric Evans commented on CASSANDRA-3424:

This change didn't do what it was supposed to, and it introduced a breaking CQL change, (which
has since made it into stable release updates(!)).  If we'd have caught this before it was
rolled into a release, I'd say it warranted an immediate -1 and a revert.

We haven't been doing nearly as well as I'd hoped in keeping stability promises, but I might
be satisfied to call the original behavior buggy, and the intended behavior of this change
as the fix, if it could be made to work the way intended (to return the result _if_ the row
exists).  Can anyone see a way to accomplish that?
> Selecting just the row_key returns nil instead of just the row_key
> ------------------------------------------------------------------
>                 Key: CASSANDRA-3424
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.0.0
>            Reporter: Kelley Reynolds
>            Assignee: Jonathan Ellis
>            Priority: Minor
>              Labels: cql
>             Fix For: 1.0.3
>         Attachments: 3424-v2.txt, CASSANDRA-3424.patch
> CREATE KEYSPACE CassandraCQLTestKeyspace WITH strategy_class='org.apache.cassandra.locator.SimpleStrategy'
AND strategy_options:replication_factor=1
> USE CassandraCQLTestKeyspace
> CREATE COLUMNFAMILY row_key_validation_cf_ascii (id ascii PRIMARY KEY, test_column text)
> INSERT INTO row_key_validation_cf_ascii (id, test_column) VALUES ('test string', 'test')
> # Works as expected
> SELECT * FROM row_key_validation_cf_ascii WHERE id = 'test string'
> # Returns an empty result, unexpected
> SELECT id FROM row_key_validation_cf_ascii WHERE id = 'test string'

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message