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

[jira] [Updated] (FLINK-30884) GetTable from Flink catalog should be judged whether it is a sink table

     [ https://issues.apache.org/jira/browse/FLINK-30884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

yuanfenghu updated FLINK-30884:
-------------------------------
    Priority: Major  (was: Blocker)

> GetTable from Flink catalog should be judged whether it is a sink table
> -----------------------------------------------------------------------
>
>                 Key: FLINK-30884
>                 URL: https://issues.apache.org/jira/browse/FLINK-30884
>             Project: Flink
>          Issue Type: Improvement
>          Components: Table SQL / API, Table SQL / Planner
>    Affects Versions: 1.16.1
>            Reporter: yuanfenghu
>            Priority: Major
>
> I want to say that when I use a third-party persistent catalog to manage the metadata of my persistent table,
> I may want to judge the options of the table I need to generate by whether it is a sink table
> For example when using kafka connector
> When I use kafka as source table,
> The following parameters are required:
> offset, properties.group.id, etc.
> When I use kafka as the sink representation, I will pass in some parameters only about the sink table, for example:
> sink.delivery-guarantee
> sink.partitioner
> So why can't we add a switch to tell the catalog this information, which is very useful in platform development! !
>  



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