accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tim Reardon (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-1734) Mutation is hard to check in unit tests
Date Mon, 14 Oct 2013 11:44:41 GMT

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

Tim Reardon commented on ACCUMULO-1734:
---------------------------------------

The behavior described in this ticket was fixed by ACCUMULO-1626. Mutatation.equals() now
serializes both Mutations prior to checking.

> 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
>
> [~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)

Mime
View raw message