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

Timo Walther resolved FLINK-8866.
---------------------------------
       Resolution: Fixed
    Fix Version/s: 1.6.0

Fixed in 1.6.0:

9597248a41b34e126aac6a807651b1d376dc6de1 
[FLINK-8866] [table] Create unified interfaces to configure and instatiate 
TableSinks

abbb89059f2a83705f41e405da14073800fb1870
[FLINK-8866] [table] Merge table source/sink/format factories

09fbfdfa76b068fcc8de249fe7cdcd01fd1f350e
[FLINK-8866] [table] Move table type out of descriptors

0e5ac4d791a8e35b3e65836bd08c8f96fd900e0b
[FLINK-8866] [table] Make source/sink factories environment-dependent

> 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
>             Fix For: 1.6.0
>
>
> 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)

Reply via email to