Deserialization failure handling #15
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a work in progress thing, just wanted to share ASAP for everyone to get the idea.
Relevant changes
KafkaDynamicTableFactory
defines the new table options (scan.deser.failure-handler
,scan.deser.failure-topic
) and passes their value.KafkaDynamicSource
in this context is just a connecting layer that passes through the newly added information.DynamicKafkaDeserializationSchema
is modified, a newly addeddeserWithFailureHandling
method now can handle the exceptions accordingly.TODO
deserFailureTarget
is now an empty shell, which should be aKafkaProducer
, that has to be initialized accordingly.upsert-kafka
classes too.