cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-5034) Refactor to introduce Mutation Container in write path
Date Sat, 02 Feb 2013 07:04:13 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-5034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13569456#comment-13569456
] 

Jonathan Ellis commented on CASSANDRA-5034:
-------------------------------------------

Is the goal to just refuse triggers against counter CFs?  Because I don't think we need more
abstraction for that.  We already have fairly substantial overhead on updates internally,
adding more seems like the wrong direction to me.
                
> Refactor to introduce Mutation Container in write path
> ------------------------------------------------------
>
>                 Key: CASSANDRA-5034
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5034
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 2.0
>            Reporter: Vijay
>            Assignee: Vijay
>            Priority: Minor
>             Fix For: 2.0
>
>         Attachments: 0001-CASSANDRA-5034.patch
>
>
> For triggers we need to identify if the batch mutations contain counters, if present
we cannot apply the BM with triggers safely. Hence we wanted this refactor, the idea is also
to improve code reuse.
> https://github.com/Vijay2win/cassandra/blob/1311/src/java/org/apache/cassandra/thrift/MutationContainer.java
> We thought (reviewer: Gary) it is better to separate these 2 patches, hence this ticket.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message