[
https://issues.apache.org/jira/browse/FLINK-21236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17278502#comment-17278502
]
Jark Wu commented on FLINK-21236:
---------------------------------
Currently, we heavily use the endian put/get methods on MemorySegment. We may
need to extract that logic into a UnsafeUtils before not using
{{HeapMemorySegment}}.
> Don't explicitly use HeapMemorySegment in raw format serde
> ----------------------------------------------------------
>
> Key: FLINK-21236
> URL: https://issues.apache.org/jira/browse/FLINK-21236
> Project: Flink
> Issue Type: Improvement
> Components: Table SQL / Planner
> Affects Versions: 1.12.0
> Reporter: Kurt Young
> Priority: Major
> Fix For: 1.13.0
>
>
> `RawFormatDeserializationSchema` and `RawFormatSerializationSchema`
> explicitly used `HeapMemorySegment`, and in a typical batch job,
> `HybridMemorySegment` will also be loaded and used as managed memory. This
> will prevent Class Hierarchy Analysis (CHA) to optimize the function call of
> MemorySegment. More details can be found here:
> [https://flink.apache.org/news/2015/09/16/off-heap-memory.html]
> We can use `ByteBuffer` instead of `HeapMemorySegment`.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
