[
https://issues.apache.org/jira/browse/FLINK-14807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17051891#comment-17051891
]
Caizhi Weng commented on FLINK-14807:
-------------------------------------
Hi dear Flink community!
I've implemented a POC of my Table#collect design. (Currently it is called
Table#collect2 to avoid compilation problems with some tests in
flink-table-planner. This will be fixed later.) You can download the patch from
the attachment. [^table-collect-draft.patch]
The collect iterator is not implemented very carefully. It will now directly
throws a RuntimeException when the job restarts. I'll deal with the versions
and tokens later and add at least once / exactly once semantics.
> Add Table#collect api for fetching data to client
> -------------------------------------------------
>
> Key: FLINK-14807
> URL: https://issues.apache.org/jira/browse/FLINK-14807
> Project: Flink
> Issue Type: New Feature
> Components: Table SQL / API
> Affects Versions: 1.9.1
> Reporter: Jeff Zhang
> Priority: Major
> Labels: usability
> Fix For: 1.11.0
>
> Attachments: table-collect-draft.patch, table-collect.png
>
>
> Currently, it is very unconvinient for user to fetch data of flink job unless
> specify sink expclitly and then fetch data from this sink via its api (e.g.
> write to hdfs sink, then read data from hdfs). However, most of time user
> just want to get the data and do whatever processing he want. So it is very
> necessary for flink to provide api Table#collect for this purpose.
>
> Other apis such as Table#head, Table#print is also helpful.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
