[
https://issues.apache.org/jira/browse/OAK-277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Guggisberg resolved OAK-277.
-----------------------------------
Resolution: Duplicate
fixed through resolution of OAK-1017
> identical nodes with different content hash ids
> -----------------------------------------------
>
> Key: OAK-277
> URL: https://issues.apache.org/jira/browse/OAK-277
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: mk
> Reporter: Stefan Guggisberg
> Assignee: Stefan Guggisberg
> Priority: Minor
>
> the current implementation internally uses a HashMap to represent the
> properties of a node and child node entries collections.
> the sha-1 content hash is based on the byte stream serialization of the node
> state. properties are serialized by iterating over the entrySet collection of
> the HashMap. since HashMap doesn't guarantee any specific iteration order
> it's possible that 2 HashMaps containing the same mappings
> (map1.equals(maps2) == true) return the entries in different order, thus
> resulting in different content hashes.
> the iteration order needs obviously to be normalized when serializing the
> entries.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
