[
https://issues.apache.org/jira/browse/ACCUMULO-4062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15014321#comment-15014321
]
Josh Elser commented on ACCUMULO-4062:
--------------------------------------
As far as I understand it, I believe that's the case. Would be easy to check.
I'd imagine that'd be the common case we run into (inadvertently sending
equivalent mutations, than purely "equal" mutations). Maybe there's sort of
trick we could play with Mutation to make it efficient and smarter in terms of
equivalence? I haven't thought about this at all, but it would be a very neat
algorithm. I wonder if HBase or Cassandra have anything like that.
> 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)
