[
https://issues.apache.org/jira/browse/FLINK-40485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18135148#comment-18135148
]
Sumin Joo commented on FLINK-40485:
-----------------------------------
Hi [~raminqaf] ,
For the Flink 2.4 release, I'm checking the impact of partially completed
FLIPs. It looks like UUID raw format support and documentation are still open.
Could you confirm whether the changes already merged can ship without these
remaining tasks, and whether they affect existing behavior for users who do not
use the new types?
Thanks!
> FLIP 604: Complete VARIANT primitive coverage with UUID and timestamps
> ----------------------------------------------------------------------
>
> Key: FLINK-40485
> URL: https://issues.apache.org/jira/browse/FLINK-40485
> Project: Flink
> Issue Type: New Feature
> Components: API / Core, API / Type Serialization System, Table SQL /
> API
> Reporter: Ramin Gharib
> Assignee: Ramin Gharib
> Priority: Major
>
> Implements FLIP-604:
> https://cwiki.apache.org/confluence/spaces/FLINK/pages/446070993/
> FLIP-521 shipped VARIANT with primitive codes 0-16. Four Parquet/Spark variant
> codes remain, and code 20 requires a Flink UUID type that does not exist yet:
> {code:java}
> code 17 time without tz (µs) -> TIME(3)
> code 18 timestamp with tz (ns) -> TIMESTAMP_LTZ(9)
> code 19 timestamp without tz (ns) -> TIMESTAMP(9)
> code 20 uuid (16-byte big-endian) -> UUID (new type) {code}
> This umbrella tracks two independent tracks: a native UUID type and
> the four new VARIANT codes. They meet only at the UUID variant cast.
> Relates to FLINK-37922 (FLIP-521).
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
