DBZ-2056 Using AsciiDoc listing syntax, allowing for attribute replacement
This commit is contained in:
parent
1bad1d27a8
commit
5625e1838d
@ -297,7 +297,8 @@ The message contains a logical representation of the table schema.
|
|||||||
|
|
||||||
The example of the message is:
|
The example of the message is:
|
||||||
|
|
||||||
```json
|
[source,json,indent=0,subs="attributes"]
|
||||||
|
----
|
||||||
{
|
{
|
||||||
"schema": {
|
"schema": {
|
||||||
...
|
...
|
||||||
@ -391,7 +392,7 @@ The example of the message is:
|
|||||||
]
|
]
|
||||||
}
|
}
|
||||||
}
|
}
|
||||||
```
|
----
|
||||||
|
|
||||||
The fields
|
The fields
|
||||||
|
|
||||||
@ -406,7 +407,8 @@ The fields
|
|||||||
|
|
||||||
The schema change messages use as the key the name of the database to which the changes apply:
|
The schema change messages use as the key the name of the database to which the changes apply:
|
||||||
|
|
||||||
```json
|
[source,json,indent=0,subs="attributes"]
|
||||||
|
----
|
||||||
{
|
{
|
||||||
"schema": {
|
"schema": {
|
||||||
"type": "struct",
|
"type": "struct",
|
||||||
@ -424,7 +426,7 @@ The schema change messages use as the key the name of the database to which the
|
|||||||
"databaseName": "TESTDB"
|
"databaseName": "TESTDB"
|
||||||
}
|
}
|
||||||
}
|
}
|
||||||
```
|
----
|
||||||
|
|
||||||
=== Events
|
=== Events
|
||||||
|
|
||||||
|
@ -264,7 +264,8 @@ The message contains a logical representation of the table schema.
|
|||||||
|
|
||||||
The example of the message is:
|
The example of the message is:
|
||||||
|
|
||||||
```json
|
[source,json,indent=0,subs="attributes"]
|
||||||
|
----
|
||||||
{
|
{
|
||||||
"schema": {
|
"schema": {
|
||||||
...
|
...
|
||||||
@ -358,7 +359,7 @@ The example of the message is:
|
|||||||
]
|
]
|
||||||
}
|
}
|
||||||
}
|
}
|
||||||
```
|
----
|
||||||
|
|
||||||
The fields
|
The fields
|
||||||
|
|
||||||
@ -373,7 +374,8 @@ The fields
|
|||||||
|
|
||||||
The schema change messages use as the key the name of the database to which the changes apply:
|
The schema change messages use as the key the name of the database to which the changes apply:
|
||||||
|
|
||||||
```json
|
[source,json,indent=0,subs="attributes"]
|
||||||
|
----
|
||||||
{
|
{
|
||||||
"schema": {
|
"schema": {
|
||||||
"type": "struct",
|
"type": "struct",
|
||||||
@ -391,7 +393,7 @@ The schema change messages use as the key the name of the database to which the
|
|||||||
"databaseName": "ORCLPDB1"
|
"databaseName": "ORCLPDB1"
|
||||||
}
|
}
|
||||||
}
|
}
|
||||||
```
|
----
|
||||||
|
|
||||||
[[events]]
|
[[events]]
|
||||||
=== Events
|
=== Events
|
||||||
|
@ -190,7 +190,8 @@ The message contains a logical representation of the table schema.
|
|||||||
|
|
||||||
The example of the message is:
|
The example of the message is:
|
||||||
|
|
||||||
```json
|
[source,json,indent=0,subs="attributes"]
|
||||||
|
----
|
||||||
{
|
{
|
||||||
"schema": {
|
"schema": {
|
||||||
...
|
...
|
||||||
@ -284,7 +285,7 @@ The example of the message is:
|
|||||||
]
|
]
|
||||||
}
|
}
|
||||||
}
|
}
|
||||||
```
|
----
|
||||||
|
|
||||||
The fields
|
The fields
|
||||||
|
|
||||||
@ -299,7 +300,8 @@ The fields
|
|||||||
|
|
||||||
The schema change messages use as the key the name of the database to which the changes apply:
|
The schema change messages use as the key the name of the database to which the changes apply:
|
||||||
|
|
||||||
```json
|
[source,json,indent=0,subs="attributes"]
|
||||||
|
----
|
||||||
{
|
{
|
||||||
"schema": {
|
"schema": {
|
||||||
"type": "struct",
|
"type": "struct",
|
||||||
@ -317,7 +319,7 @@ The schema change messages use as the key the name of the database to which the
|
|||||||
"databaseName": "testDB"
|
"databaseName": "testDB"
|
||||||
}
|
}
|
||||||
}
|
}
|
||||||
```
|
----
|
||||||
|
|
||||||
=== Events
|
=== Events
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user