DBZ-5128 Assign unique anchor ID to recently added topic routing option

This commit is contained in:
Bob Roldan 2022-05-12 18:01:37 -04:00 committed by Jiri Pechanec
parent bd11b5a7e9
commit 3d308da31a

View File

@ -194,7 +194,7 @@ Specify `false` if you do not want the transformation to add a key field. For e
| |
|Specifies a regular expression for determining the value of the inserted key field in terms of the groups captured by the expression specified for `key.field.regex`. For the SMT to apply this expression, `key.enforce.uniqueness` must be `true`, which is the default. |Specifies a regular expression for determining the value of the inserted key field in terms of the groups captured by the expression specified for `key.field.regex`. For the SMT to apply this expression, `key.enforce.uniqueness` must be `true`, which is the default.
|[[by-logical-table-router-logical-table-cache-size]]xref:by-logical-table-router-logical-table-cache-size[`schema.name.adjustment.mode`] |[[by-logical-table-router-schema-name-adjustment-mode]]xref:by-logical-table-router-schema-name-adjustment-mode[`schema.name.adjustment.mode`]
|`avro` |`avro`
|Specify how the message key schema names derived from the resulting topic name should be adjusted for compatibility with the message converter used by the connector, including: `avro` replaces the characters that cannot be used in the Avro type name with underscore (default), `none` does not apply any adjustment. |Specify how the message key schema names derived from the resulting topic name should be adjusted for compatibility with the message converter used by the connector, including: `avro` replaces the characters that cannot be used in the Avro type name with underscore (default), `none` does not apply any adjustment.