SteNicholas opened a new pull request #13333:
URL: https://github.com/apache/flink/pull/13333
## What is the purpose of the change
*Currently, `debezium-json` format only support deserialization, but not
support serialization, which is not convenient for users to writing changelogs
to an message queue. The serialization for `debezium-json` could follow the
json strcuture of debezium, but should consider currently Flink can't combine
`UPDATE_BEFORE` and `UPDATE_AFTER` into a single `UPDATE` message. This could
encode `UPDATE_BEFORE` and `UDPATE_AFTER` as `DELETE` and `INSERT` debezium
messages. Therefore, this could support serialization for `debezium-json`
format*
## Brief change log
- *Add `DebeziumJsonSerializationSchema` which serialization schema from
Flink Table/SQL internal data structure `RowData` to Debezium JSON.*
- *`DebeziumJsonFormatFactory` supports `createEncodingFormat` with
creating EncodingFormat for `DebeziumJsonSerializationSchema`.*
## Verifying this change
- *`DebeziumJsonSerDeSchemaTest` add test cases for
`DebeziumJsonSerializationSchema` to verify the serialization schema to
Debezium JSON.*
- *`DebeziumJsonFormatFactoryTest` add test cases for creating
`DebeziumJsonSerializationSchema` and `DebeziumJsonDeserializationSchema` to
verify the serialization and deserialization schema for
`DebeziumJsonFormatFactory`.*
## Does this pull request potentially affect one of the following parts:
- Dependencies (does it add or upgrade a dependency): (yes / **no**)
- The public API, i.e., is any changed class annotated with
`@Public(Evolving)`: (yes / **no**)
- The serializers: (yes / **no** / don't know)
- The runtime per-record code paths (performance sensitive): (yes / **no**
/ don't know)
- Anything that affects deployment or recovery: JobManager (and its
components), Checkpointing, Kubernetes/Yarn/Mesos, ZooKeeper: (yes / **no** /
don't know)
- The S3 file system connector: (yes / **no** / don't know)
## Documentation
- Does this pull request introduce a new feature? (yes / **no**)
- If yes, how is the feature documented? (**not applicable** / docs /
JavaDocs / not documented)
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
[email protected]
