DBZ-8090 Defines new snippets folder attribute
This commit is contained in:
parent
d4431e17e4
commit
9a40ff3b77
@ -25,6 +25,7 @@ asciidoc:
|
||||
community: true
|
||||
registry: 'Apicurio Registry'
|
||||
registry-name-full: Apicurio API and Schema Registry
|
||||
snippetsdir: /snippets
|
||||
link-avro-serialization: 'configuration/avro.adoc'
|
||||
link-cassandra-connector: 'connectors/cassandra.adoc'
|
||||
link-cloud-events: 'integrations/cloudevents.adoc'
|
||||
|
@ -28,12 +28,12 @@ For example, suppose you have a `products` {data-collection} that contains the f
|
||||
|
||||
If you want an incremental snapshot of the `products` {data-collection} to include only the data items where `color=blue`, you can use the following SQL statement to trigger the snapshot:
|
||||
|
||||
include::{partialsdir}/modules/snippets/{context}-frag-signaling-fq-table-formats.adoc[leveloffset=+1,tags=snapshot-additional-conditions-example]
|
||||
include::{snippetsdir}/{context}-frag-signaling-fq-table-formats.adoc[leveloffset=+1,tags=snapshot-additional-conditions-example]
|
||||
|
||||
The `additional-conditions` parameter also enables you to pass conditions that are based on more than one column.
|
||||
For example, using the `products` {data-collection} from the previous example, you can submit a query that triggers an incremental snapshot that includes the data of only those items for which `color=blue` and `quantity>10`:
|
||||
|
||||
include::{partialsdir}/modules/snippets/{context}-frag-signaling-fq-table-formats.adoc[leveloffset=+1,tags=snapshot-multiple-additional-conditions-example]
|
||||
include::{snippetsdir}/{context}-frag-signaling-fq-table-formats.adoc[leveloffset=+1,tags=snapshot-multiple-additional-conditions-example]
|
||||
|
||||
The following example, shows the JSON for an incremental snapshot event that is captured by a connector.
|
||||
|
||||
|
@ -25,4 +25,4 @@ Specify {data-collection} names by using the format `{collection-container}.{dat
|
||||
|===
|
||||
|
||||
The following example shows a typical `stop-snapshot` Kafka message:
|
||||
include::{partialsdir}/modules/snippets/{context}-frag-signaling-fq-table-formats.adoc[leveloffset=+1,tags=stopping-incremental-snapshot-kafka-example]
|
||||
include::{snippetsdir}/{context}-frag-signaling-fq-table-formats.adoc[leveloffset=+1,tags=stopping-incremental-snapshot-kafka-example]
|
||||
|
@ -26,7 +26,7 @@ INSERT INTO _<signalTable>_ (id, type, data) values (_'<id>'_, 'stop-snapshot',
|
||||
+
|
||||
For example,
|
||||
+
|
||||
include::{partialsdir}/modules/snippets/{context}-frag-signaling-fq-table-formats.adoc[leveloffset=+1,tags=stopping-incremental-snapshot-example]
|
||||
include::{snippetsdir}/{context}-frag-signaling-fq-table-formats.adoc[leveloffset=+1,tags=stopping-incremental-snapshot-example]
|
||||
+
|
||||
The values of the `id`, `type`, and `data` parameters in the signal command correspond to the {link-prefix}:{link-signalling}#debezium-signaling-description-of-required-structure-of-a-signaling-data-collection[fields of the signaling {data-collection}].
|
||||
+
|
||||
|
@ -56,10 +56,8 @@ When the snapshot request includes an `additional-conditions` property, the `dat
|
||||
`SELECT * FROM _<data-collection>_ WHERE _<filter>_ ....`
|
||||
|
||||
For example, given a `products` {data-collection} with the columns `id` (primary key), `color`, and `brand`, if you want a snapshot to include only content for which `color='blue'`, when you request the snapshot, you could add the `additional-conditions` property to filter the content:
|
||||
|
||||
include::{partialsdir}/modules/snippets/{context}-frag-signaling-fq-table-formats.adoc[leveloffset=+1,tags=triggering-incremental-snapshot-kafka-addtl-cond-example]
|
||||
include::{snippetsdir}/{context}-frag-signaling-fq-table-formats.adoc[leveloffset=+1,tags=triggering-incremental-snapshot-kafka-addtl-cond-example]
|
||||
|
||||
You can also use the `additional-conditions` property to pass conditions based on multiple columns.
|
||||
For example, using the same `products` {data-collection} as in the previous example, if you want a snapshot to include only the content from the `products` {data-collection} for which `color='blue'`, and `brand='MyBrand'`, you could send the following request:
|
||||
|
||||
include::{partialsdir}/modules/snippets/{context}-frag-signaling-fq-table-formats.adoc[leveloffset=+1,tags=triggering-incremental-snapshot-kafka-multi-addtl-cond-example]
|
||||
include::{snippetsdir}/{context}-frag-signaling-fq-table-formats.adoc[leveloffset=+1,tags=triggering-incremental-snapshot-kafka-multi-addtl-cond-example]
|
||||
|
@ -13,8 +13,7 @@ To specify the {data-collection}s to include in the snapshot, provide a `data-co
|
||||
The `data-collections` array for an incremental snapshot signal has no default value.
|
||||
If the `data-collections` array is empty, {prodname} interprets the empty array to mean that no action is required, and it does not perform a snapshot.
|
||||
|
||||
include::{partialsdir}/modules/snippets/{context}-frag-signaling-fq-table-formats.adoc[leveloffset=+1,tags=fq-table-name-format-note]
|
||||
|
||||
include::{snippetsdir}/{context}-frag-signaling-fq-table-formats.adoc[leveloffset=+1,tags=fq-table-name-format-note]
|
||||
.Prerequisites
|
||||
|
||||
* {link-prefix}:{link-signalling}#debezium-signaling-enabling-source-signaling-channel[Signaling is enabled]. +
|
||||
@ -32,7 +31,7 @@ INSERT INTO _<signalTable>_ (id, type, data) VALUES (_'<id>'_, _'<snapshotType>'
|
||||
+
|
||||
For example,
|
||||
+
|
||||
include::{partialsdir}/modules/snippets/{context}-frag-signaling-fq-table-formats.adoc[leveloffset=+1,tags=snapshot-signal-example]
|
||||
include::{snippetsdir}/{context}-frag-signaling-fq-table-formats.adoc[leveloffset=+1,tags=snapshot-signal-example]
|
||||
+
|
||||
The values of the `id`,`type`, and `data` parameters in the command correspond to the {link-prefix}:{link-signalling}#debezium-signaling-description-of-required-structure-of-a-signaling-data-collection[fields of the signaling {data-collection}].
|
||||
+
|
||||
|
Loading…
Reference in New Issue
Block a user