[
https://issues.apache.org/jira/browse/FLINK-30884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17684104#comment-17684104
]
luoyuxia commented on FLINK-30884:
----------------------------------
I think now I understand your case. It's valid, but I still don't think it's
Catalog's responsibility to . Catalog is designed to store table ignoring table
source or sink.
For you case, I think you can implement it in DynamicTableSink/
DynamicTableSource, you can generate these information in method
getScanRuntimeProvider.
> 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)
