[
https://issues.apache.org/jira/browse/ACCUMULO-3044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christopher Tubbs resolved ACCUMULO-3044.
-----------------------------------------
Resolution: Abandoned
Closing this stale issue. If this is still a problem, please create a new issue
or PR at https://github.com/apache/accumulo
> ConditionalMutation should support conditional updates
> ------------------------------------------------------
>
> Key: ACCUMULO-3044
> URL: https://issues.apache.org/jira/browse/ACCUMULO-3044
> Project: Accumulo
> Issue Type: Improvement
> Components: client, tserver
> Affects Versions: 1.6.0
> Reporter: Ryan Leary
> Priority: Major
>
> Currently, the ConditionalMutation object operates on a single row, and
> applies updates if and only if a set of Conditions are met.
> A new type of ConditionalMutation which operates on a single row and applies
> an update if and only if a set of Conditions for that particular update would
> be more flexible.
> This behavior is possible currently by creating a new ConditionalMutation for
> each update. In the case where there are a large number of updates for a
> single row, however, there is a steep penalty paid due to the row-level
> locking. Another acceptable solution to this ticket would be optimizing the
> ConditionalWriter to apply multiple conditional mutations on the same row
> within the same atomic lock. The order of execution would need to be
> guaranteed.
> The API would look something like:
> {code}
> ConditionalMutation cm = new ConditionalMutation(rowKey);
> cm.put(Iterable<Condition>, CF, CQ, CV, Val);
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
