[
https://issues.apache.org/jira/browse/CASSANDRA-6055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylvain Lebresne resolved CASSANDRA-6055.
-----------------------------------------
Resolution: Invalid
We have no simple way to to support null values for partition key columns
internally. If we don't allow it, I don't really see the point of allowing
selecting on them, except maybe confusing users.
bq. This query is good in SQL
This is irrelevant, CQL is not SQL and we don't intend to support syntax that
does not make sense for CQL 'just because it's valid SQL'.
> 'Bad Request: Invalid null value for partition key part' on SELECT .. WHERE
> key IN (val,NULL)
> ---------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-6055
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6055
> Project: Cassandra
> Issue Type: Bug
> Environment: cqlsh, pdo_cassandra
> Reporter: Sergey Nagaytsev
> Labels: cql3
>
> Query: SELECT * FROM user WHERE key IN(uuid,NULL);
> Table:
> CREATE COLUMNFAMILY user (
> KEY uuid PRIMARY KEY,
> name text,
> note text,
> avatar text,
> email text,
> phone text,
> login text,
> pw text,
> st text
> );
> Logs: Nothing, last message hours ago.
> This query is good in SQL and so is generated by DB abstraction library. Fix
> on applications sides is multiplying of work.
--
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
