[
https://issues.apache.org/jira/browse/CASSANDRA-6477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14625077#comment-14625077
]
T Jake Luciani edited comment on CASSANDRA-6477 at 7/13/15 6:15 PM:
--------------------------------------------------------------------
What I'm saying is we can't insert nulls into clustering or partition keys. we
don't support it. So we can't put multiple non-pk columns into a materialized
view PK we (of course they can be in the non-PK columns of the view)
{code}
cqlsh:test> create table test(foo text, bar text, baz text, PRIMARY
KEY(foo,bar));
cqlsh:test> INSERT INTO test(foo, bar, baz) VALUES ( 'a', 'b', 'c');
cqlsh:test> INSERT INTO test(foo, bar, baz) VALUES ( 'a', null, 'c');
InvalidRequest: code=2200 [Invalid query] message="Invalid null value for
clustering key part bar"
cqlsh:test> INSERT INTO test(foo, bar, baz) VALUES ( null, 'b', 'c');
InvalidRequest: code=2200 [Invalid query] message="Invalid null value for
partition key part foo"
cqlsh:test>
{code}
was (Author: tjake):
What I'm saying is we can't insert nulls into clustering or partition keys. we
don't support it. So we can't put multiple non-pk columns into a materialized
view PK we (of course they can be in the non-PK columns of the view)
> Materialized Views (was: Global Indexes)
> ----------------------------------------
>
> Key: CASSANDRA-6477
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6477
> Project: Cassandra
> Issue Type: New Feature
> Components: API, Core
> Reporter: Jonathan Ellis
> Assignee: Carl Yeksigian
> Labels: cql
> Fix For: 3.0 beta 1
>
> Attachments: test-view-data.sh, users.yaml
>
>
> Local indexes are suitable for low-cardinality data, where spreading the
> index across the cluster is a Good Thing. However, for high-cardinality
> data, local indexes require querying most nodes in the cluster even if only a
> handful of rows is returned.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
