[
https://issues.apache.org/jira/browse/FLINK-9852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timo Walther resolved FLINK-9852.
---------------------------------
Resolution: Fixed
Fix Version/s: 1.6.0
Fixed in 1.7.0: 6fcc1e9a868ff3ce2bd0376b6b3493a08c7b604c
Fixed in 1.6.0: 7bb07e4e74ed7167cd98599af1a851afa1d77252
> Expose descriptor-based sink creation and introduce update mode
> ---------------------------------------------------------------
>
> Key: FLINK-9852
> URL: https://issues.apache.org/jira/browse/FLINK-9852
> Project: Flink
> Issue Type: New Feature
> Components: Table API & SQL
> Affects Versions: 1.6.0
> Reporter: Timo Walther
> Assignee: Timo Walther
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.6.0
>
>
> Currently, only a table source can be created using the unified table
> descriptors with {{tableEnv.from(...)}}. A similar approach should be
> supported for defining sinks or even both types at the same time.
> I suggest the following syntax:
> {code}
> tableEnv.connect(Kafka(...)).registerSource("name")
> tableEnv.connect(Kafka(...)).registerSink("name")
> tableEnv.connect(Kafka(...)).registerSourceAndSink("name")
> {code}
> A table could then access the registered source/sink.
> We need to introduce a new update-mode property in order to distinguish
> between append, retract, and upsert table sources and sinks.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
