This will be a very useful addition to Flink UI. Thanks Rui for starting a
FLIP for this improvement.

Regards
Venkata krishnan


On Wed, Mar 27, 2024 at 4:49 AM Muhammet Orazov
<mor+fl...@morazow.com.invalid> wrote:

> Hello Rui,
>
> Thanks for the proposal! It looks good!
>
> I have minor clarification from my side:
>
> The execution mode is also used for the DataStream API [1],
> would that also affect/hide the DataStream execution mode
> if we remove it from the WebUI?
>
> Best,
> Muhammet
>
> [1]:
>
> https://urldefense.com/v3/__https://nightlies.apache.org/flink/flink-docs-release-1.18/docs/dev/datastream/execution_mode/__;!!IKRxdwAv5BmarQ!eFyqVJyje_8hu1vMSUwKGBsj8vqsFDisEvJ5AxPV0LduhhHWF3rPKYEEE-09biA0unFbfMy5AVQZMgBv1AOa5oTHmcYlkUE$
>
>
> On 2024-03-27 06:23, Rui Fan wrote:
> > Hi flink developers,
> >
> > I'd like to start a discussion to discuss FLIP-441:
> > Show the JobType and remove Execution Mode on Flink WebUI[1].
> >
> > Currently, the jobType has 2 types in Flink: STREAMING and BATCH.
> > They work on completely different principles, such as: scheduler,
> > shuffle, join, etc. These differences lead to different troubleshooting
> > processes, so when users are maintaining a job or troubleshooting,
> > it's needed to know whether the current job is a STREAMING or
> > BATCH job. Unfortunately, Flink WebUI doesn't expose it to the
> > users so far.
> >
> > Also, Execution Mode is related to DataSet api, it has been marked
> > as @Deprecated in FLINK-32258 (1.18), but it's still shown in Flink
> > WebUI.
> >
> > Looking forward to hearing more thoughts about it! Thank you~
> >
> > [1]
> https://urldefense.com/v3/__https://cwiki.apache.org/confluence/x/agrPEQ__;!!IKRxdwAv5BmarQ!eFyqVJyje_8hu1vMSUwKGBsj8vqsFDisEvJ5AxPV0LduhhHWF3rPKYEEE-09biA0unFbfMy5AVQZMgBv1AOa5oTHayPyFj8$
> > [2]
> https://urldefense.com/v3/__https://issues.apache.org/jira/browse/FLINK-32558__;!!IKRxdwAv5BmarQ!eFyqVJyje_8hu1vMSUwKGBsj8vqsFDisEvJ5AxPV0LduhhHWF3rPKYEEE-09biA0unFbfMy5AVQZMgBv1AOa5oTHftYeOLE$
> >
> > Best,
> > Rui
>

Reply via email to