accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bill Havanki (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-1734) Mutation is hard to check in unit tests
Date Fri, 27 Sep 2013 17:06:02 GMT

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

Bill Havanki commented on ACCUMULO-1734:
----------------------------------------

I'm not sure that it would. I could write a quick test case to find out.

I would rather find some solution that doesn't change the API at all, so I'm still working
on it. I can provide more details under ACCUMULO-1627 when I have something that I think is
decent.
                
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message