[
https://issues.apache.org/jira/browse/ACCUMULO-1051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Faro updated ACCUMULO-1051:
---------------------------------
Labels: newbie (was: )
Status: Patch Available (was: Open)
I wasn't able to recreate the failing test case since I think the underlying
HashMap was consistently hashing the keys a and b, however the HashSet API
indicates that the Iterator will not return keys in any particular order. So I
went ahead and added the test case and changed the implementation of auths to
use a TreeSet so it will always iterate over the keys consistently regardless
of insertion order.
> Authorizations has inconsistent serialization
> ---------------------------------------------
>
> Key: ACCUMULO-1051
> URL: https://issues.apache.org/jira/browse/ACCUMULO-1051
> Project: Accumulo
> Issue Type: Bug
> Components: client
> Reporter: Christopher Tubbs
> Assignee: Christopher Tubbs
> Priority: Trivial
> Labels: newbie
> Fix For: 1.5.0
>
>
> The same set of authorizations may not serialize to the same value each time,
> if specified in a different order when constructed (like new
> Authorizations("a", "b") and new Authorizations("b", "a")), because
> serialization reproducibility depends on the insert order in the underlying
> HashSet.
> So, one could get the following to happen:
> {code:java}
> true == auths1.equals(auths2) &&
> !auths1.serialize().equals(auths2.serialize());
> {code}
--
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
