[
https://issues.apache.org/jira/browse/FLINK-15182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16994575#comment-16994575
]
ShenDa commented on FLINK-15182:
--------------------------------
[~jark] it's very glad to see the intention of implementing a unified
FileSystem TableSink.
But, we also find the code in filesystem connector is deprecated, and the
flink-table module contains CsvTableSink&CsvTableSource. So we think of the
current hierarchical structure of FileSystem Connector needs to be refactored.
Besides, may be, the CSV should be kinds of format like json, but not be a
individual TableSource or TableSink.
> Add FileTableSink based on StreamingFileSink
> --------------------------------------------
>
> Key: FLINK-15182
> URL: https://issues.apache.org/jira/browse/FLINK-15182
> Project: Flink
> Issue Type: Improvement
> Components: Connectors / FileSystem
> Reporter: ShenDa
> Priority: Major
>
> Flink already has FileSystem connector that can sink data into specified file
> system, but it just writes data to a target path without bukcet and it can't
> configure file rolling policy neither. We can use StreamingFileSink to avoid
> those shortcomings instead, however, the StreamingFileSink is a SinkFunction
> that users have to implement their processing logic with DataStreamAPI.
> Therefore, we want to add a new FileTableSink based on StreamingFileSink.
> This will help us connect file system by using TableAPI&SQL. But according to
> the two ways of StreamingFileSink to sinking data, bulk format and row
> format, it comes a question to us. Does the FileTableSink have to support
> bulk format and row format simultaneously? Or separating this sink into two
> table sinks, BulkFileTableSink and RowFileTableSink, which write data by
> using one format respectively?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
