[
https://issues.apache.org/jira/browse/FLINK-14807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17060077#comment-17060077
]
Caizhi Weng commented on FLINK-14807:
-------------------------------------
Hi [~sewen]
The client receives the data through REST calls as well. The aggregate function
it submits will fetch and return a batch of new results. These results passes
through REST API as the response and are handed back to the clients.
This procedure is triggered by the user. If the user calls the {{next}} method
of the iterator and all the last batch of results have been totally consumed,
the iterator will call the REST API to fetch a new batch of results. If
currently no new results exist, the iterator will periodically poll the REST
API until the job ends or a new batch of results arrives.
> 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)
