[
https://issues.apache.org/jira/browse/FLINK-37722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhanghao Chen updated FLINK-37722:
----------------------------------
Description:
Currently, PojoSerializer will first create a new POJO instance and initialize
all the fields (in the createInstance() method), then deserialize and set
fields. The field initialization with in the createInstance() method is
redundant, as all fields will be set later during deserialization anyway. We
should eliminate it for better performance.
The TupleSerializer has already applied similar techique, see the usage of
TupleSerializer#instantiateRaw.
was:Currently, PojoSerializer will first create a new POJO instance and
initialize all the fields (in the createInstance() method), then deserialize
and set fields. The field initialization with in the createInstance() method is
redundant, as all fields will be set later during deserialization anyway. We
should eliminate it for better performance.
> Eliminate redundant field initialization when deserializing POJOs
> -----------------------------------------------------------------
>
> Key: FLINK-37722
> URL: https://issues.apache.org/jira/browse/FLINK-37722
> Project: Flink
> Issue Type: Sub-task
> Components: API / Type Serialization System
> Reporter: Zhanghao Chen
> Priority: Major
>
> Currently, PojoSerializer will first create a new POJO instance and
> initialize all the fields (in the createInstance() method), then deserialize
> and set fields. The field initialization with in the createInstance() method
> is redundant, as all fields will be set later during deserialization anyway.
> We should eliminate it for better performance.
> The TupleSerializer has already applied similar techique, see the usage of
> TupleSerializer#instantiateRaw.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
