[
https://issues.apache.org/jira/browse/CASSANDRA-2614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13049308#comment-13049308
]
Sylvain Lebresne commented on CASSANDRA-2614:
---------------------------------------------
Turns out there is a tiny hiccup.
For a Deletion (inside a thrift Mutation), the timestamp is required to be set
if the CF is a regular one, but not if it is a counter CF. But more
importantly, for counter CF, the timestamp should be a server generated
timestamp.
If we allow row to mix counters and regular columns, then when facing a
Deletion for a full row, there is no way to accommodate those two requirements.
It would kind of be a shame of not doing this because of Deletion, but I don't
see a good way around this (other than changing the API, which would move that
ticket to 1.0).
Ideas ?
> 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
