[
https://issues.apache.org/jira/browse/CASSANDRA-1693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12930160#action_12930160
]
Pavel Yaskevich commented on CASSANDRA-1693:
--------------------------------------------
The trick I'm thinking of here will be if no comparator is set for column
family we will try to use preferred and it if fails we will use default (same
goes for validator and keys)?...
Or we can drop DEFAULT part here it will make things very simple - will be able
just to set comparator/sub_comparator fields for CfDef and for keys just store
comparator in special map (sorted by column family) to use instead of
ByteBufferUtil.string(ks.key, Charsets.UTF_8) in printSliceList method.
> add cli support for assuming CF comparator, validator
> -----------------------------------------------------
>
> Key: CASSANDRA-1693
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1693
> Project: Cassandra
> Issue Type: Improvement
> Components: Tools
> Affects Versions: 0.7 beta 1
> Reporter: Jonathan Ellis
> Assignee: Pavel Yaskevich
> Priority: Minor
> Fix For: 0.7.0
>
>
> Similar to what we did for CASSANDRA-1603 for column-level metadata, we'd
> like to be able to add client-side metadata for a CF w/o actually updating
> the CF definition. Suggestions for syntax?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
