alexey.rassokhin/tet123
1
0
Fork 0
Code Issues Pull Requests 1 Packages Projects Releases Wiki Activity

DBZ-2021 Cleanup deprecations

Browse Source
This commit is contained in:
Chris Cranford 2020-05-19 13:29:52 -04:00 committed by GitHub
parent 8c6403ff5f
commit 901b19c23c
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 0 additions and 47 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

47
documentation/modules/ROOT/pages/configuration/event-flattening.adoc
View File

@ -226,53 +226,6 @@ In the simplified Kafka record, the SMT prefixes the metadata field names with a
To add metadata to a simplified Kafka record that is for a `DELETE` operation, you must also configure `delete.handling.mode=rewrite`.
ifdef::community[]
// Do not include deprecated content in downstream doc
== Determine original operation [DEPRECATED]
_The `operation.header` option is deprecated and scheduled for removal. Please use add.headers instead. If both add.headers and operation.header are specified, the latter will be ignored._
When a Kafka record is flattened the final result won't show whether it was an insert, update or first read
(deletions can be detected via tombstones or rewrites, see link:#options-for-configuring-extractnewrecordstate-transformation[Configuration options]).
To solve this problem {prodname} offers an option to propagate the original operation via a header added to the Kafka record.
To enable this feature the option `operation.header` must be set to `true`.
[source]
----
transforms=unwrap,...
transforms.unwrap.type=io.debezium.transforms.ExtractNewRecordState
transforms.unwrap.operation.header=true
----
The possible values are the ones from the `op` field of the original change event.
endif::community[]
ifdef::community[]
// Do not include deprecated content in downstream doc
== Adding source metadata fields [DEPRECATED]
_The `add.source.fields` option is deprecated and scheduled for removal. Please use add.fields instead. If both add.fields and add.source.fields are specified, the latter will be ignored._
The SMT can optionally add metadata fields from the original change event's `source` structure to the final flattened record (prefixed with "__"). This functionality can be used to add things like the table from the change event, or connector-specific fields like the Postgres LSN field. For more information on what's available in the source structure see xref:connectors/index.adoc[the documentation for each connector].
For example, the configuration
----
transforms=unwrap,...
transforms.unwrap.type=io.debezium.transforms.ExtractNewRecordState
transforms.unwrap.add.source.fields=table,lsn
----
will add
----
{ "__table": "MY_TABLE", "__lsn": "123456789", ...}
----
to the final flattened record.
For `DELETE` events, this option is only supported when the `delete.handling.mode` option is set to "rewrite".
[id="configuration-options"]
== Configuration options