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

Posted to issues@flink.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2021/03/18 04:47:00 UTC

[jira] [Updated] (FLINK-21236) Don't explicitly use HeapMemorySegment in raw format serde

     [ https://issues.apache.org/jira/browse/FLINK-21236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

ASF GitHub Bot updated FLINK-21236:
-----------------------------------
    Labels: pull-request-available  (was: )

> 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
>            Assignee: Xintong Song
>            Priority: Major
>              Labels: pull-request-available
>             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)