You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "dalongliu (Jira)" <ji...@apache.org> on 2025/07/07 07:48:00 UTC

[jira] [Commented] (FLINK-37997) Release Testing Instructions: Verify FLIP-521: Integrating Variant Type into Flink

    [ https://issues.apache.org/jira/browse/FLINK-37997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18001720#comment-18001720 ] 

dalongliu commented on FLINK-37997:
-----------------------------------

Close this Jira because https://issues.apache.org/jira/browse/FLINK-37997 has been created.

> Release Testing Instructions: Verify FLIP-521: Integrating Variant Type into Flink
> ----------------------------------------------------------------------------------
>
>                 Key: FLINK-37997
>                 URL: https://issues.apache.org/jira/browse/FLINK-37997
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Table SQL / Planner
>    Affects Versions: 2.1.0
>            Reporter: dalongliu
>            Assignee: suxuan
>            Priority: Blocker
>              Labels: release-testing
>             Fix For: 2.1.0
>
>
> This issue aims to partially verify FLIP-521.
> Flink SQL API now supports the Variant type. And it supports `PARSE_JSON` and `TRY_PARSE_JSON` to parse a JSON string to a Variant.
> We may need to cover the following types of test cases:
> Test 1: Confirm that you can use SQL API to create a Print sink with a Variant column.
> Test 2: Confirm that `PARSE_JSON` and `TRY_PARSE_JSON` can parse a JSON string to a Variant.
> Follow up the test for https://issues.apache.org/jira/browse/FLINK-37922



--
This message was sent by Atlassian Jira
(v8.20.10#820010)