You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@flink.apache.org by "Yingjie Cao (Jira)" <ji...@apache.org> on 2020/06/22 10:14:00 UTC

[jira] [Created] (FLINK-18408) BinaryRowData should use de-/serialization method of MemorySegment with explicit endianness

Yingjie Cao created FLINK-18408:
-----------------------------------

             Summary: 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


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)