[
https://issues.apache.org/jira/browse/FLINK-14807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16977227#comment-16977227
]
Kostas Kloudas edited comment on FLINK-14807 at 11/19/19 12:33 PM:
-------------------------------------------------------------------
[~zjffdu] [~sewen] if I understand the issue correctly, this is about an API
call to be added to the Table API. The Executor/JobClient does not affect APIs
yet and they are not exposed.
When the {{JobClient}} is exposed, then the user would be able to request the
accumulators of a job, at any time, which will allow to have a "collect-like"
behaviour (assuming that the results fit in memory).
was (Author: kkl0u):
[~zjffdu] [~sewen] if I understand the issue correctly, this is about an API
call to be added to the Table API. The Executor/JobClient does not affect APIs
yet and they are not exposed.
When the {{JobClient}} is exposed, then the user would be able to request the
accumulators of a job, at any time, which will allow to have a "collect-like"
behaviour.
> 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
>
> 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)
