Skip to content

Commit 077ac47

Browse files
author
your proper name
committed
(DOCSP-42962) Unnested 3 tips, 1 example and 1 important admonition in table.
1 parent 6fa0ae5 commit 077ac47

File tree

1 file changed

+29
-42
lines changed

1 file changed

+29
-42
lines changed

source/source-connector/configuration-properties/kafka-topic.txt

+29-42
Original file line numberDiff line numberDiff line change
@@ -50,12 +50,9 @@ Settings
5050
The destination topic name is composed of the ``topic.prefix``
5151
value followed by the database and collection names, separated by the value
5252
specified in the ``topic.separator`` property.
53-
54-
.. seealso::
55-
56-
:ref:`Topic Naming Prefix <source-usage-example-topic-naming>`
57-
usage example
58-
53+
|
54+
| To learn more, see the example in :ref:`Topic Naming Prefix <topic-naming-prefix-example>`.
55+
|
5956
| **Default**: ``""``
6057
| **Accepted Values**: A string composed of ASCII alphanumeric
6158
characters including ".", "-", and "_"
@@ -69,12 +66,9 @@ Settings
6966
The destination topic name is composed of the database and
7067
collection names followed by the ``topic.suffix`` value,
7168
separated by the value specified in the ``topic.separator`` property.
72-
73-
.. seealso::
74-
75-
:ref:`Topic Naming Suffix <source-usage-example-topic-naming>`
76-
usage example
77-
69+
|
70+
| To learn more, see the example in :ref:`Topic Naming Suffix <topic-naming-suffix-example>`.
71+
|
7872
| **Default**: ``""``
7973
| **Accepted Values**: A string composed of ASCII alphanumeric
8074
characters including ".", "-", and "_"
@@ -86,16 +80,14 @@ Settings
8680
| Specifies a JSON mapping between change stream document
8781
:manual:`namespaces </reference/glossary/#std-term-namespace>`
8882
and topic names.
89-
90-
.. tip:: Namespace Mapping Behavior
91-
92-
You can specify complex mappings by using the
93-
``topic.namespace.map`` property. This property supports regex
94-
and wildcard matching. To learn more about these behaviors and
95-
view examples, see the :ref:`Topic Namespace Map
96-
<topic-naming-namespace-map>` section of the Topic Naming
97-
page.
98-
83+
|
84+
| You can specify complex mappings by using the
85+
``topic.namespace.map`` property. This property supports regex
86+
and wildcard matching. To learn more about these behaviors and
87+
view examples, see the :ref:`Topic Namespace Map
88+
<topic-naming-namespace-map>` section of the Topic Naming
89+
page.
90+
|
9991
| **Default**: ``""``
10092
| **Accepted Values**: A valid JSON object
10193

@@ -113,29 +105,24 @@ Settings
113105
#. ``collection``
114106
#. ``topic.suffix``
115107

116-
.. example::
117-
118-
The following configuration instructs the connector to publish
119-
change stream documents from the ``coll`` collection of the
120-
``db`` database to the ``prefix-db-coll``
121-
topic:
108+
| For example, the following configuration instructs the connector to publish
109+
change stream documents from the ``coll`` collection of the
110+
``db`` database to the ``prefix-db-coll`` topic:
122111

123-
.. code-block:: properties
124-
:copyable: false
112+
.. code-block:: properties
113+
:copyable: false
125114

126-
topic.prefix=prefix
127-
database=db
128-
collection=coll
129-
topic.separator=-
115+
topic.prefix=prefix
116+
database=db
117+
collection=coll
118+
topic.separator=-
130119

131-
.. important:: Topic Separator and Topic Namespace Map
132-
133-
When you use the ``topic.separator`` property, keep in mind that it
134-
does not affect how you define the ``topic.namespace.map`` property.
135-
The ``topic.namespace.map`` property uses MongoDB
136-
:manual:`namespaces </reference/glossary/#std-term-namespace>`
137-
which you must always specify with a ``"."`` character to separate
138-
the database and collection name.
120+
| :gold:`IMPORTANT:` When you use the ``topic.separator`` property, keep in mind that it
121+
does not affect how you define the ``topic.namespace.map`` property.
122+
The ``topic.namespace.map`` property uses MongoDB
123+
:manual:`namespaces </reference/glossary/#std-term-namespace>`
124+
which you must always specify with a ``.`` character to separate
125+
the database and collection name.
139126

140127
|
141128
| **Default**: ``"."``

0 commit comments

Comments
 (0)