[
https://issues.apache.org/jira/browse/FLINK-18408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17336150#comment-17336150
]
Flink Jira Bot commented on FLINK-18408:
----------------------------------------
This issue was labeled "stale-major" 7 ago and has not received any updates so
it is being deprioritized. If this ticket is actually Major, please raise the
priority and ask a committer to assign you the issue or revive the public
discussion.
> BinaryRowData should use de-/serialization method of MemorySegment with
> explicit endianness
> -------------------------------------------------------------------------------------------
>
> Key: FLINK-18408
> URL: https://issues.apache.org/jira/browse/FLINK-18408
> Project: Flink
> Issue Type: Bug
> Components: Table SQL / Runtime
> Reporter: Yingjie Cao
> Priority: Major
> Labels: stale-major
>
> I notice that classes like BinaryRowData use de-/serialization method of
> MemorySegment without explicit endianness, I think this is not safe if we
> serialize some data on one machine and deserialize on another machine with
> different endianness. To be one the safe side, I think we should use
> de-/serialization method of MemorySegment with explicit endianness. What do
> you think? (BinaryRowWriter may have the same issue and there may be some
> other classes also suffer from this but I did not notice)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
