reswqa opened a new pull request, #24129:
URL: https://github.com/apache/flink/pull/24129
…ther to force registration of Avro serializer with Kryo
## What is the purpose of the change
*Currently the avro serializers is registered with Kryo if flink-avro is on
the classpath. This also happens if avro isn't even used by the job, be it due
to a mistake in the dependencies setup, branching or flink-avro being in lib.
This forces users to always provide flink-avro going forward for affected jobs,
because on recovery Flink complains if any of the Kryo serializers cant be
loaded.*
## Brief change log
- *Introduce a new config option that controls whether or not register
`avro` to `KryoSerializer`.*
## Verifying this change
Basically covered by existing tests, while also adding some unit tests.
## Does this pull request potentially affect one of the following parts:
- Dependencies (does it add or upgrade a dependency): no
- The public API, i.e., is any changed class annotated with
`@Public(Evolving)`: yes
- The serializers: yes
- The runtime per-record code paths (performance sensitive): no
- Anything that affects deployment or recovery: JobManager (and its
components), Checkpointing, Kubernetes/Yarn, ZooKeeper: no
- The S3 file system connector: no
## Documentation
- Does this pull request introduce a new feature? no
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
