[ 
https://issues.apache.org/jira/browse/FLINK-11199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17219592#comment-17219592
 ] 

Matthias commented on FLINK-11199:
----------------------------------

[~becket_qin] [~RuidongLi]: I came across this issue as part of the Engine team 
backlog grooming. Can you give some update on the state as it seems to idle for 
some time. Should we revive it updating the proposal and moving the discussion 
to the mailing list as proposed by [~trohrmann] in 
[FLINK-12425|https://issues.apache.org/jira/browse/FLINK-12425?focusedCommentId=16847395&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16847395]?

> Support interactive programming in Flink
> ----------------------------------------
>
>                 Key: FLINK-11199
>                 URL: https://issues.apache.org/jira/browse/FLINK-11199
>             Project: Flink
>          Issue Type: New Feature
>          Components: Table SQL / API
>    Affects Versions: 2.0.0
>            Reporter: Jiangjie Qin
>            Assignee: Jiangjie Qin
>            Priority: Major
>
> Generally speaking, Flink applications may consist of one or more jobs, and 
> the jobs may want to share the data with others. In Flink, the jobs in the 
> same application are independent and share nothing among themselves. If a 
> Flink application involves several sequential steps, each step (as an 
> independent job) will have to write its intermediate results to an external 
> sink, so that its results can be used by the following step (job) as sources. 
> Although this works, that means users have to provide external storage and 
> explicitly write/read from it. 
>  
> To improve the user experience, we would like to propose adding support of 
> interactive programming in Flink. We would like to start with Table API. And 
> the discussion thread is following:
> https://docs.google.com/document/d/1d4T2zTyfe7hdncEUAxrlNOYr4e5IMNEZLyqSuuswkA0/edit?ts=5bf639d9#



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to