[
https://issues.apache.org/jira/browse/FLINK-34354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhanghao Chen updated FLINK-34354:
----------------------------------
Description:
This issue aims to verify
[FLIP-398|https://cwiki.apache.org/confluence/display/FLINK/FLIP-398%3A+Improve+Serialization+Configuration+And+Usage+In+Flink].
Volunteers can verify it by following the [doc
changes|https://github.com/apache/flink/pull/24230]. Basically, two parts need
to be verfied:
# The old way of configuring serialization via hard-code method calls still
works:
** ExecutionConfig#registerType (for both POJO and generic types)
** ExecutionConfig#addDefaultKryoSerializer
** ExecutionConfig#registerTypeWithKryoSerializer
# The new way of configuring serialization via config option
[pipeline.serialization-config|https://nightlies.apache.org/flink/flink-docs-master/docs/deployment/config/#pipeline-serialization-config]
also works for:
** Regieter serializer for POJO types
** Register Kryo serializer for generic types
** Register Kryo serializer as the default Kryo serializer for types
** Register custom type info factories
was:
This issue aims to verify
[FLIP-398|https://cwiki.apache.org/confluence/display/FLINK/FLIP-398%3A+Improve+Serialization+Configuration+And+Usage+In+Flink].
Volunteers can verify it by following the [doc
changes|https://github.com/apache/flink/pull/24230]. Basically, two parts need
to be verfied:
# The old way of configuring serialization via hard-code method calls still
works:
** ExecutionConfig#registerType (for both POJO and generic types)
** ExecutionConfig#addDefaultKryoSerializer
** ExecutionConfig#registerTypeWithKryoSerializer
# The new way of configuring serialization via config option
[pipeline.serialization-config|https://nightlies.apache.org/flink/flink-docs-master/docs/deployment/config/#pipeline-serialization-config]
also works for:
** Regieter serializer for POJO types
** Register Kryo serializer for generic types
** Register Kryo serializer as the default Kryo serializer for types
** Register custome type info factories
> Release Testing: Verify FLINK-34037 Improve Serialization Configuration and
> Usage in Flink
> ------------------------------------------------------------------------------------------
>
> Key: FLINK-34354
> URL: https://issues.apache.org/jira/browse/FLINK-34354
> Project: Flink
> Issue Type: Sub-task
> Components: API / Type Serialization System
> Affects Versions: 1.19.0
> Reporter: Zhanghao Chen
> Priority: Blocker
> Labels: release-testing
> Fix For: 1.19.0
>
>
> This issue aims to verify
> [FLIP-398|https://cwiki.apache.org/confluence/display/FLINK/FLIP-398%3A+Improve+Serialization+Configuration+And+Usage+In+Flink].
> Volunteers can verify it by following the [doc
> changes|https://github.com/apache/flink/pull/24230]. Basically, two parts
> need to be verfied:
> # The old way of configuring serialization via hard-code method calls still
> works:
> ** ExecutionConfig#registerType (for both POJO and generic types)
> ** ExecutionConfig#addDefaultKryoSerializer
> ** ExecutionConfig#registerTypeWithKryoSerializer
> # The new way of configuring serialization via config option
> [pipeline.serialization-config|https://nightlies.apache.org/flink/flink-docs-master/docs/deployment/config/#pipeline-serialization-config]
> also works for:
> ** Regieter serializer for POJO types
> ** Register Kryo serializer for generic types
> ** Register Kryo serializer as the default Kryo serializer for types
> ** Register custom type info factories
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
