[
https://issues.apache.org/jira/browse/ACCUMULO-1051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13578047#comment-13578047
]
Kevin Faro commented on ACCUMULO-1051:
--------------------------------------
Good point ... sorry I am still trying to get my hands around the code.
Would it be better to sort auths in checkAuths and store the authorizations in
sorted order in the authList? Then in serialize, just iterate over the
authList instead of auths. It would take slightly longer for object creation,
but then the sort would only happen once.
John ... what class/classes are failing to build?
> 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: Kevin Faro
> Priority: Trivial
> Labels: newbie
> Fix For: 1.5.0
>
> Attachments: accumulo-1051.patch
>
>
> 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
