[
https://issues.apache.org/jira/browse/FLINK-14807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17046357#comment-17046357
]
Kurt Young commented on FLINK-14807:
------------------------------------
[~becket_qin] Your first point is actually the root of complexity. According to
current analysis, JM should be the one who is responsible to retrieve the
results, this would make things more complex and not straightforward, e.g.
lacking of communication channel between tasks and JM. Right now we have to
depend on `GlobalAggregateManager` to transfer the socket server's address, and
it seems to be the only way.
And not dealing with client failure doesn't make things much more simpler, most
of the complexity comes from task failure and maybe even JM failure.
> 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.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)
