[
https://issues.apache.org/jira/browse/FLINK-8866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shuyi Chen updated FLINK-8866:
------------------------------
Description:
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.
was:
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 "tableType" 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.
> 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
>
> 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)
