[
https://issues.apache.org/jira/browse/CASSANDRA-2614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13030638#comment-13030638
]
Sylvain Lebresne commented on CASSANDRA-2614:
---------------------------------------------
To be more specific, the idea is for instance to allow counter in a non-counter
CF with something like
{noformat}
column_metadata = [
{column_name: first, validation_class: UTF8Type},
{column_name: last, validation_class: UTF8Type},
{column_name: friends, validation_class: CounterColumnType} ];
{noformat}
In which case we know when we expect a counter and when we do not. Moreover the
code already handle mixing counter and non counter mutations in a batch_mutate,
so most of the handling of the different write path is already there. We will
still have to "extract" the counter column for this so that it goes through the
correct write path, but that can be done while we translate the thrift
structures to our internal representations.
> create Column and CounterColumn in the same column family
> ---------------------------------------------------------
>
> Key: CASSANDRA-2614
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2614
> Project: Cassandra
> Issue Type: New Feature
> Components: Core
> Reporter: Dave Rav
> Assignee: Sylvain Lebresne
> Priority: Minor
> Fix For: 0.8.1
>
>
> create Column and CounterColumn in the same column family
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
