[
https://issues.apache.org/jira/browse/CASSANDRA-1773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12964421#action_12964421
]
Jonathan Ellis commented on CASSANDRA-1773:
-------------------------------------------
bq. if CF was marked as Super it was still using "cf_def.comparator"
you're right, subcomparator is the correct behavior. it doesn't make sense to
add metadata to the supercolumn itself since supercolumns do not have byte[]
values.
committed.
> Prevent creation of column_metadata inconsistent with comparator
> ----------------------------------------------------------------
>
> Key: CASSANDRA-1773
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1773
> Project: Cassandra
> Issue Type: Improvement
> Affects Versions: 0.7.0 rc 1
> Reporter: Jonathan Ellis
> Assignee: Pavel Yaskevich
> Priority: Minor
> Fix For: 0.7.0
>
> Attachments: 1773-server-side.txt, CASSANDRA-1773.patch
>
>
> {code}
> create keyspace clitest with replication_factor = 1 and placement_strategy =
> 'org.apache.cassandra.locator.SimpleStrategy';
> use clitest;
> create column family bar with column_type = 'Super' and comparator =
> 'TimeUUIDType' and subcomparator = 'UTF8Type';
> create column family foo with column_type = 'Super' and comparator =
> 'TimeUUIDType' and subcomparator = 'UTF8Type' and
> column_metadata=[{column_name:col1, validation_class:UTF8Type},
> {column_name:col2, validation_class:UTF8Type}];
> {code}
> then, "describe keyspace clitest" will give "UUIDs must be exactly 16 bytes"
> because it tries to run "col1" through the comparator getString.
> We should check that column names in metadata match the comparator when
> updating metadata, and also check that the column names are sane if we update
> the comparator itself.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
