raminqaf commented on code in PR #29760:
URL: https://github.com/apache/flink/pull/29760#discussion_r4467041535
##########
docs/content/docs/connectors/table/formats/raw.md:
##########
@@ -112,12 +112,26 @@ Format Options
<td>String</td>
<td>Specify the line delimiter for splitting incoming messages into
multiple rows during
deserialization. When set, each incoming message is decoded using
'raw.charset' and then split
- by this delimiter; one row is emitted per segment. During serialization,
the delimiter bytes
+ by this delimiter; one row is emitted per segment. A
<code>VARIANT</code> column is instead split
+ on the UTF-8 bytes of the delimiter, without decoding the message.
During serialization, the delimiter bytes
Review Comment:
added.
##########
docs/content/docs/connectors/table/formats/raw.md:
##########
@@ -112,12 +112,26 @@ Format Options
<td>String</td>
<td>Specify the line delimiter for splitting incoming messages into
multiple rows during
deserialization. When set, each incoming message is decoded using
'raw.charset' and then split
- by this delimiter; one row is emitted per segment. During serialization,
the delimiter bytes
+ by this delimiter; one row is emitted per segment. A
<code>VARIANT</code> column is instead split
+ on the UTF-8 bytes of the delimiter, without decoding the message.
During serialization, the delimiter bytes
are appended to each serialized value. Common values are '\n' (newline)
or '||'.
<br><strong>Note:</strong> When the same delimiter is configured for
both serialization and
deserialization, the two are round-trip compatible: a trailing delimiter
appended by the
serializer is automatically stripped during deserialization.</td>
</tr>
+ <tr>
+ <td><h5>raw.variant-encoding</h5></td>
+ <td>optional</td>
+ <td style="word-wrap: break-word;">json</td>
+ <td>Enum</td>
+ <td>Specify how a <code>VARIANT</code> column is encoded. Valid values
are 'json' and 'binary'.
+ 'json' reads and writes a UTF-8 JSON document. It is convenient, because
people and other systems
+ can read and write JSON, but it is lossy: JSON has no type for dates,
times, timestamps, bytes or
Review Comment:
done
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
