davidradl commented on code in PR #26740:
URL: https://github.com/apache/flink/pull/26740#discussion_r2179958574
##########
docs/content.zh/docs/dev/table/types.md:
##########
@@ -1458,6 +1460,39 @@ DataTypes.DESCRIPTOR()
{{< /tab >}}
{{< /tabs >}}
+#### `VARIANT`
+
+Data type of semi-structured data.
+
+The type supports storing any semi-structured data, including `ARRAY`, `MAP`,
and scalar types.
+`VARIANT` can only store `MAP` types with keys of type `STRING`. The data type
of the fields are
+stored in the data structure, which is close to the semantics of JSON.
Compared to `ROW` and
+`STRUCTURED` type, `VARIANT` type has the flexibility that supports highly
nested and evolving
Review Comment:
nit: that supports -> to support.
When we say "has the flexibility that supports highly nested and evolving
schema". I suggest highlighting in the docs:
- explain more about the highly nested schema
- explain more about how this helps with schema evolution. For example by
contrasting with a schema registry way of handdling schema evolution.
##########
docs/content.zh/docs/dev/table/types.md:
##########
@@ -1458,6 +1460,39 @@ DataTypes.DESCRIPTOR()
{{< /tab >}}
{{< /tabs >}}
+#### `VARIANT`
+
+Data type of semi-structured data.
+
+The type supports storing any semi-structured data, including `ARRAY`, `MAP`,
and scalar types.
+`VARIANT` can only store `MAP` types with keys of type `STRING`. The data type
of the fields are
+stored in the data structure, which is close to the semantics of JSON.
Compared to `ROW` and
+`STRUCTURED` type, `VARIANT` type has the flexibility that supports highly
nested and evolving
Review Comment:
nit: that supports -> to support.
When we say "has the flexibility that supports highly nested and evolving
schema". I suggest highlighting in the docs:
- explain more about the highly nested schema
- explain more about how this helps with schema evolution. For example by
contrasting with a schema registry way of handling schema evolution.
--
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]
