[
https://issues.apache.org/jira/browse/OAK-4864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15532990#comment-15532990
]
Francesco Mari commented on OAK-4864:
-------------------------------------
A quick-and-dirty solution to this issue would be to set a specific byte order
by calling
[ByteBuffer.order|https://docs.oracle.com/javase/7/docs/api/java/nio/ByteBuffer.html#order(java.nio.ByteOrder)]
on every {{ByteBuffer}} we use. A better solution would be to use our utility
class to embed {{ByteBuffer}} and ensure consistency.
> The binary format is influenced by the endianness of the system
> ----------------------------------------------------------------
>
> Key: OAK-4864
> URL: https://issues.apache.org/jira/browse/OAK-4864
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: segment-tar, segmentmk
> Reporter: Francesco Mari
>
> The Segment Store implementations use {{ByteBuffer}} to read and write data
> in many places. Methods of the {{ByteBuffer}} that read or write data types
> bigger than one byte always do so "according to the current byte order". This
> means that the binary format is not portable across systems with different
> endianness.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
