You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "luoyuxia (Jira)" <ji...@apache.org> on 2022/12/09 08:15:00 UTC

[jira] [Comment Edited] (FLINK-30325) the column lost comments, also find some issue ,but that commit is not mr. i have some diff solution

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

luoyuxia edited comment on FLINK-30325 at 12/9/22 8:14 AM:
-----------------------------------------------------------

I'm afraid of not. It'll break compatibility which we defintly want to guarantee in bug-fix version like 1.14.4.

It won't be accepted by Flink community.


was (Author: luoyuxia):
I'm afraid of not. It'll break compatibility which we defintly want to guarantee in bug-fix version like 1.14.4.

> the column lost comments, also find some issue ,but that commit is not mr. i have some diff  solution
> -----------------------------------------------------------------------------------------------------
>
>                 Key: FLINK-30325
>                 URL: https://issues.apache.org/jira/browse/FLINK-30325
>             Project: Flink
>          Issue Type: Improvement
>          Components: Connectors / Hive, Table SQL / Planner
>    Affects Versions: 1.14.3, 1.16.0
>         Environment: flink: 1.14.3
>            Reporter: blackpighe
>            Priority: Major
>              Labels: columns, comments
>             Fix For: 1.14.3
>
>   Original Estimate: 504h
>  Remaining Estimate: 504h
>
> In the process of using flink in the company, column level comment were found to be lost, and there was also an issue in the community discussing these issues, but they try to modify the structure of the table schema to fix it. I have a better solution here. The basic idea is to upgrade TableSchema to ResolvedSchema. However, there are some problems if an external component uses a lower version of flink and may not have a ResolvedSchema.



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