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

DBZ-2539 Conditionalize :toc: entry to render in upstream doc only.

Browse Source
This commit is contained in:
Bob Roldan 2020-09-15 12:11:01 -04:00 committed by Chris Cranford
parent 240ec966d5
commit c621777113
2 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
documentation/modules/ROOT/pages/configuration/content-based-routing.adoc
View File

@ -4,7 +4,7 @@
// Title: Routing change event records to topics according to event content
[id="content-based-routing"]
= Content-based routing
ifdef::community[]
:toc:
:toc-placement: macro
:linkattrs:
@ -12,7 +12,7 @@
:source-highlighter: highlight.js
toc::[]
endif::community[]
By default, {prodname} streams all of the change events that it reads from a table to a single static topic.
However, there might be situations in which you might want to reroute selected events to other topics, based on the event content.
The process of routing messages based on their content is described in the https://www.enterpriseintegrationpatterns.com/patterns/messaging/ContentBasedRouter.html[Content-based routing] messaging pattern.

4
documentation/modules/ROOT/pages/configuration/filtering.adoc
View File

@ -4,7 +4,7 @@
// Title: Filtering Debezium change event records
[id="message-filtering"]
= Message Filtering
ifdef::community[]
:toc:
:toc-placement: macro
:linkattrs:
@ -12,7 +12,7 @@
:source-highlighter: highlight.js
toc::[]
endif::community[]
By default, {prodname} delivers every data change event that it receives to the Kafka broker.
However, in many cases, you might be interested in only a subset of the events emitted by the producer.
To enable you to process only the records that are relevant to you, {prodname} provides the _filter_ simple message transform (SMT).