Thanks Junhan for driving this. It a great improvement for the batch jobs. I'm looking forward to this feature in our internal use case. +1 for it.
One more question: Are each attempts of the TaskManager or JobManager pods (if failure occurs) all be shown in the ui ? Best, Aitozi. Yang Wang <danrtsey...@gmail.com> 于2022年6月16日周四 19:10写道： > Thanks Xintong for the explanation. > > It makes sense to leave the discussion about job result store in a > dedicated thread. > > > Best, > Yang > > Xintong Song <tonysong...@gmail.com> 于2022年6月16日周四 13:40写道： > > > My impression of JobResultStore is more about fault tolerance and high > > availability. Using it for providing information to users sounds worth > > exploring. We probably need more time to think it through. > > > > Given that it doesn't conflict with what we have proposed in this FLIP, > I'd > > suggest considering it as a separate thread and exclude it from the scope > > of this one. > > > > Best, > > > > Xintong > > > > > > > > On Thu, Jun 16, 2022 at 11:43 AM Yang Wang <danrtsey...@gmail.com> > wrote: > > > > > This is a very useful feature both for finished streaming and batch > jobs. > > > > > > Except for the WebUI & REST API improvements, I am curious whether we > > could > > > also integrate some critical information(e.g. latest checkpoint) into > the > > > job result store[1]. > > > I am just feeling this is also somehow related with "Completed Jobs > > > Information Enhancement". > > > And I think the history server is not necessary for all the scenarios > > > especially when users only want to check the job execution result. > > > > > > [1]. > > > > > > > > > https://cwiki.apache.org/confluence/display/FLINK/FLIP-194%3A+Introduce+the+JobResultStore > > > > > > > > > Best, > > > Yang > > > > > > Xintong Song <tonysong...@gmail.com> 于2022年6月15日周三 15:37写道： > > > > > > > Thanks Junhan, > > > > > > > > +1 for the proposed improvements. > > > > > > > > Best, > > > > > > > > Xintong > > > > > > > > > > > > > > > > On Wed, Jun 15, 2022 at 3:16 PM Yangze Guo <karma...@gmail.com> > wrote: > > > > > > > > > Thanks for driving this, Junhan. > > > > > > > > > > I think it's a valuable usability improvement for both streaming > and > > > > > batch users. Looking forward to the community feedback. > > > > > > > > > > Best, > > > > > Yangze Guo > > > > > > > > > > > > > > > > > > > > On Wed, Jun 15, 2022 at 3:10 PM junhan yang < > > yangjunhan1...@gmail.com> > > > > > wrote: > > > > > > > > > > > > Hi all, > > > > > > > > > > > > I would like to open a discussion on FLIP-241: Completed Jobs > > > > Information > > > > > > Enhancement. > > > > > > > > > > > > As far as we can tell, streaming and batch users have different > > > > interests > > > > > > in probing a job. As Flink grows into a unified streaming & batch > > > > > processor > > > > > > and is adopted by more and more batch users, the user experience > of > > > > > > completed job's inspection has become more and more important. > > After > > > > > doing > > > > > > several market research, there are several potential improvements > > > > > spotted. > > > > > > > > > > > > The main purpose here is due to the involvement of WebUI & REST > API > > > > > > changes, which should be openly discussed and voted on as FLIPs. > > > > > > > > > > > > You can find more details in FLIP-241 document[1]. Looking > forward > > to > > > > > > your feedback. > > > > > > > > > > > > [1] https://cwiki.apache.org/confluence/x/dRD1D > > > > > > > > > > > > Best regards, > > > > > > Junhan > > > > > > > > > > > > > > >
