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

DBZ-3141 Typo fixes

Browse Source 
Co-authored-by: Gunnar Morling <gunnar.morling@googlemail.com>
This commit is contained in:
Jiri Pechanec 2021-03-16 13:34:51 +01:00 committed by Gunnar Morling
parent eb0c5ccb45
commit f48e7261af
3 changed files with 6 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
documentation/modules/ROOT/nav.adoc
View File

@ -13,7 +13,7 @@
** xref:configuration/filtering.adoc[Message Filtering]
** xref:configuration/content-based-routing.adoc[Content-Based Routing]
** xref:configuration/topic-auto-create-config.adoc[Customizing Topic Auto-Creation]
** xref:configuration/signalling.adoc[Sending signals to Debezium]
** xref:configuration/signalling.adoc[Sending Signals to Debezium]
* Connectors
** xref:connectors/index.adoc[Overview]
** xref:connectors/mysql.adoc[MySQL]

9
documentation/modules/ROOT/pages/configuration/signalling.adoc
View File

@ -20,7 +20,7 @@ This feature is currently in incubating state, i.e. exact semantics, configurati
== Overview
Sometimes it is necessary for the user to modify a connector behaviour or trigger a one-time action (e.g. snapshot of a single table).
To fullwfill such needs {prodname} provides a mechanism how to send a signal to a {prodname} connector to trigger an action.
To fulfill such needs {prodname} provides a mechanism how to send a signal to a {prodname} connector to trigger an action.
As it might be necessary to synchronize such an action with the dataflow the signal is implemented as a write to a data collection.
Signalling is disabled by default.
@ -33,8 +33,8 @@ The signalling data collection must be *explictly* added among captured data col
|Parameter | Description
|`signal.data.collection`
|Fully-qualified name of data cloection. +
The name format is connector specific.
|Fully-qualified name of data collection. +
The name format is connector specific, e.g. "some_schema.debezium_signals" in case of the {prodname} Postgres connector.
|===
@ -42,7 +42,7 @@ The name format is connector specific.
=== Data collection structure
The signalling data collection must conform to a required format.
it must contain three fields.
It must contain three fields
The naming of the fields is arbitrary and only order of the field is important.
It is recommended but not mandatory to use the field names as defined in the table below.
@ -121,4 +121,3 @@ If a placeholder `{}` is added to the message it will be replaced with streaming
|`{"message": "Signal message at offset {}"}`
|===

2
documentation/modules/ROOT/pages/connectors/oracle.adoc
View File

@ -1788,7 +1788,7 @@ It is possible to use {prodname} link:/documentation/reference/configuration/sig
The type of the schema update action is `schema-changes`.
It will update the schema of all tables enumerated in the signal parameters.
The message contain not the update to the schema but the complete new schema structure.
The message does not contain the update to the schema, but the complete new schema structure.
.Action parameters
[cols="3,9",options="header"]