You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "Tim Reardon (JIRA)" <ji...@apache.org> on 2013/10/14 13:46:41 UTC
[jira] [Resolved] (ACCUMULO-1734) Mutation is hard to check in unit
tests
[ https://issues.apache.org/jira/browse/ACCUMULO-1734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tim Reardon resolved ACCUMULO-1734.
-----------------------------------
Resolution: Fixed
Fix Version/s: 1.4.4
1.6.0
1.5.1
> Mutation is hard to check in unit tests
> ---------------------------------------
>
> Key: ACCUMULO-1734
> URL: https://issues.apache.org/jira/browse/ACCUMULO-1734
> Project: Accumulo
> Issue Type: Bug
> Components: client
> Affects Versions: 1.4.4
> Reporter: Eric Newton
> Priority: Minor
> Fix For: 1.5.1, 1.6.0, 1.4.4
>
>
> [~treardon] writes:
> {quote}
> The problem is that Mutation.equals() calls a private serialize() method that modifies the data about to be checked. I have successfully worked around this in the past by wrapping the Mutation in a new Mutation, which calls serialize under the hood:
> assertEquals(expectedMutation, new Mutation(actualMutation));
> This applies to 1.4.x, I don't know if Mutation.equals() has changed since then.
> {quote}
--
This message was sent by Atlassian JIRA
(v6.1#6144)