@@ -86,7 +86,7 @@ schema for your incoming documents, you must specify a key schema
86
86
87
87
You can enable the default key schema with the following option:
88
88
89
- .. code-block:: java
89
+ .. code-block:: properties
90
90
91
91
output.format.key=schema
92
92
@@ -182,6 +182,23 @@ following options:
182
182
output.format.value=schema
183
183
output.schema.infer.value=true
184
184
185
+ The source connector can infer schemas for incoming documents that
186
+ contain nested documents stored in arrays. Starting in Version 1.9 of the
187
+ {+connector+}, schema inference will gather the appropriate data type
188
+ for fields instead of defaulting to a ``string`` type assignment if there are
189
+ differences between nested documents described by the following cases:
190
+
191
+ - A field is present in one document but missing in another.
192
+ - A field is present in one document but ``null`` in another.
193
+ - A field is an array with elements of any type in one document but
194
+ has additional elements or elements of other data types in another.
195
+ - A field is an array with elements of any type in one document but an
196
+ empty array in another.
197
+
198
+ If field types conflict between nested documents, the connector
199
+ pushes the conflict down to the schema for the field and defaults to a
200
+ ``string`` type assignment.
201
+
185
202
.. note:: Cannot Infer Key Schema
186
203
187
204
The {+connector+} does not support key schema inference. If you want to use a key
0 commit comments