DBZ-5396 Document relational attributes in JSON schema change events

This commit is contained in:
Chris Cranford 2022-07-14 13:25:22 -04:00 committed by Chris Cranford
parent 75ad893d67
commit fdf6fc1fa3
4 changed files with 36 additions and 0 deletions

View File

@ -342,6 +342,11 @@ The message contains a logical representation of the table schema.
"autoIncremented": false, "autoIncremented": false,
"generated": false "generated": false
} }
],
"attributes": [ // <10>
{
"customAttribute": "attributeValue"
}
] ]
} }
} }
@ -400,6 +405,10 @@ a|Describes the kind of change. The value is one of the following:
|`columns` |`columns`
|Metadata for each column in the changed table. |Metadata for each column in the changed table.
|10
|`attributes`
|Custom attribute metadata for each table change.
|=== |===
In messages that the connector sends to the schema change topic, the message key is the name of the database that contains the schema change. In messages that the connector sends to the schema change topic, the message key is the name of the database that contains the schema change.

View File

@ -281,6 +281,11 @@ The message contains a logical representation of the table schema.
"autoIncremented": false, "autoIncremented": false,
"generated": false "generated": false
} }
],
"attributes": [ <11>
{
"customAttribute": "attributeValue"
}
] ]
} }
} }
@ -352,6 +357,10 @@ In the case of a table rename, this identifier is a concatenation of `_<old>_,_<
|`columns` |`columns`
|Metadata for each column in the changed table. |Metadata for each column in the changed table.
|11
|`attributes`
|Custom attribute metadata for each table change.
|=== |===
See also: xref:{link-mysql-connector}#mysql-schema-history-topic[schema history topic]. See also: xref:{link-mysql-connector}#mysql-schema-history-topic[schema history topic].

View File

@ -329,6 +329,11 @@ The message contains a logical representation of the table schema.
"autoIncremented": false, "autoIncremented": false,
"generated": false "generated": false
} }
],
"attributes": [ // <10>
{
"customAttribute": "attributeValue"
}
] ]
} }
} }
@ -386,6 +391,10 @@ In the case of a table rename, this identifier is a concatenation of `_<old>_,_<
|`columns` |`columns`
|Metadata for each column in the changed table. |Metadata for each column in the changed table.
|10
|`attributes`
|Custom attribute metadata for each table change.
|=== |===
In messages that the connector sends to the schema change topic, the message key is the name of the database that contains the schema change. In messages that the connector sends to the schema change topic, the message key is the name of the database that contains the schema change.

View File

@ -346,6 +346,11 @@ The message contains a logical representation of the table schema.
"autoIncremented": false, "autoIncremented": false,
"generated": false "generated": false
} }
],
"attributes": [ // <10>
{
"customAttribute": "attributeValue"
}
] ]
} }
} }
@ -404,6 +409,10 @@ a|Describes the kind of change. The value is one of the following:
|`columns` |`columns`
|Metadata for each column in the changed table. |Metadata for each column in the changed table.
|10
|`attributes`
|Custom attribute metadata for each table change.
|=== |===
In messages that the connector sends to the schema change topic, the key is the name of the database that contains the schema change. In messages that the connector sends to the schema change topic, the key is the name of the database that contains the schema change.