[
https://issues.apache.org/jira/browse/FLINK-8866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16531114#comment-16531114
]
ASF GitHub Bot commented on FLINK-8866:
---------------------------------------
Github user fhueske commented on the issue:
https://github.com/apache/flink/pull/6201
Hi @suez1224, that sounds good overall. :-)
A few comments:
- I would not add a user-facing property `connector.support-timestamp`
because a user chooses that by choosing the connector type. Whether the
connector supports writing a system timestamp can be an internal
field/annotation/interface of the `TableSink` that is generated from the
properties.
- Copying the timestamp to the StreamRecord timestamp field can be done
with a process function. Actually, we do that already when converting a Table
into a DataStream. Setting the flag in the Kafka TableSink should be easy.
- Not sure if `from-source` needs to be supported by the initial version.
We could just implement `from-field` for now, and handle `from-source` as a
follow up issue. Since we are approaching feature freeze, I think this might be
a good idea at this point.
What do you think?
Fabian
> Create unified interfaces to configure and instatiate TableSinks
> ----------------------------------------------------------------
>
> Key: FLINK-8866
> URL: https://issues.apache.org/jira/browse/FLINK-8866
> Project: Flink
> Issue Type: New Feature
> Components: Table API & SQL
> Reporter: Timo Walther
> Assignee: Shuyi Chen
> Priority: Major
> Labels: pull-request-available
>
> Similar to the efforts done in FLINK-8240. We need unified ways to configure
> and instantiate TableSinks. Among other applications, this is necessary in
> order to declare table sinks in an environment file of the SQL client. Such
> that the sink can be used for {{INSERT INTO}} statements.
> Below are a few major changes in mind.
> 1) Add TableSinkFactory/TableSinkFactoryService similar to
> TableSourceFactory/TableSourceFactoryService
> 2) Add a common property called "type" with values (source, sink and both)
> for both TableSource and TableSink.
> 3) in yaml file, replace "sources" with "tables", and use tableType to
> identify whether it's source or sink.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
