[
https://issues.apache.org/jira/browse/ACCUMULO-4062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15014507#comment-15014507
]
John Vines commented on ACCUMULO-4062:
--------------------------------------
Given the strict tracking we have about order of mutations coming in, it may
not be an explicit contract but it's certainly implied. If I currently add 2
mutations for the same row and column with different data, the one that comes
in last wins. The suggested change would make the result dependent on the hash
function instead.
> Change MutationSet.mutations to use HashSet
> -------------------------------------------
>
> Key: ACCUMULO-4062
> URL: https://issues.apache.org/jira/browse/ACCUMULO-4062
> Project: Accumulo
> Issue Type: Improvement
> Components: client
> Reporter: Dave Marion
>
> Change TabletServerBatchWriter.MutationSet.mutations from a
> {code}
> HashMap<String,List<Mutation>>
> {code}
> to
> {code}
> HashMap<String,HashSet<Mutation>>
> {code}
> so that duplicate mutations added by a client are not sent to the server.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
