[
https://issues.apache.org/jira/browse/CASSANDRA-7305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14009853#comment-14009853
]
Sylvain Lebresne commented on CASSANDRA-7305:
---------------------------------------------
I agree that this is not a very consistent result. It stems from the fact that
for static columns we said that when only the partition key and static columns
where selected, the user probably didn't meant to query the full partition, and
so we only query the static part of the partition, hence the result above.
In hindsight, I would agree that this is a mistake. We should make such query
scan the whole partition the same way a selection of just the partition key
still scan the full partition (and return as many results as there is rows).
And we should extend DISTINCT so user can still query the static part
efficiently.
This is going to potentially break current users of static columns however (but
they are new enough that it's probably fair game to fix early mistake rather
than carry them down indefinitely).
> CQL3, Static columns not returning rows if values are not set
> -------------------------------------------------------------
>
> Key: CASSANDRA-7305
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7305
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Reporter: Patrick Callaghan
> Assignee: Sylvain Lebresne
> Priority: Minor
>
> Just a quick note on static columns, if you create some cql rows using
> clustered columns and don't provide a value for a static column, then
> selecting the row key with the (null) static column won't return any rows.
> create table statictest( a int, b text static, c text, PRIMARY KEY (a, c));
> insert into statictest (a, c) values (1, 'test');
> select a,b from statictest;
> (0 rows)
--
This message was sent by Atlassian JIRA
(v6.2#6252)
