[FLINK-13876] Remove ExecutionConfig field from PojoSerializer

• Type: Improvement
• Status: Open
• Priority: Not a Priority
• Resolution: Unresolved
• Affects Version/s: 1.7.2, 1.8.1, 1.9.0, 1.10.0
• Component/s: API / Type Serialization System
• Labels: auto-deprioritized-major auto-deprioritized-minor
• Assignee: Unassigned
• Reporter: Dawid Wysakowicz
• Created: 27/Aug/19 15:20
• Updated: 27/Sep/23 22:35

Description

The PojoSerializers stores an instance of ExecutionConfig as internal field, even though that the only information it may ever need are the registered kryo serializers.

This has a few drawbacks:

• It blocks the evolution of ExecutionConfig as serializers where stored in a state. Therefore any change to ExecutionConfig must be backwards compatible in respect to java serialization
• It probably already introduced a bug, as upon restore the Snapshot actually recreates the serializer with an empty ExecutionConfig (see org.apache.flink.api.java.typeutils.runtime.PojoSerializerSnapshot#restoreSerializer)

I suggest to remove the field completely and adjust corresponding usages.

Issue Links

• blocks: FLINK-13857 Remove remaining UdfAnalyzer configurations
• is related to: FLINK-29379 Back (most of the) ExecutionConfig and CheckpointConfig by Configuration