Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FLINK-2205] Fix confusing entries in JM UI Job Config. section #927

Closed

Conversation

ebautistabar
Copy link
Contributor

Default display for 'Number of execution retries' is now 'deactivated' and for 'Job parallelism' is 'auto', as suggested in JIRA.

@fhueske
Copy link
Contributor

fhueske commented Jul 21, 2015

Hi @ebautistabar, thanks for the pull request!
I would also like to change the key "Number of execution retries" to "Max. number of execution retries" (or similiar) to make sure, that users understand that this is the configured max number of retries and not the number of times a task execution was actually retried.

@StephanEwen
Copy link
Contributor

The job manager UI is under rework right now, there is a new version coming up, see here:

https://github.com/apache/flink/tree/master/flink-runtime-web

This fix (if going to the old UI) would be only temporary...

Default display for 'Number of execution retries' is now 'deactivated'
and for 'Job parallelism' is 'auto', as suggested in JIRA.
@ebautistabar
Copy link
Contributor Author

Hi @fhueske, @StephanEwen, I wasn't aware of that. Just picked a starter issue to get my feet wet.

I've added the other suggested change, in case you decide to merge this while you finish the new UI. If not, please feel free to close the PR (and maybe the Jira issue, if this has already been dealt with in the new dashboard code).

@tillrohrmann
Copy link
Contributor

@ebautistabar you're the only one who can close the PR. But maybe the new web interface needs the same fixes as you've proposed for the old UI.

@StephanEwen
Copy link
Contributor

I think you can actually add the code to the current UI. It is not going to disappear in the near future, it will probably stay as a fallback variant for one more version.

You can add this functionality there. Adding it to the new web frontend is a separate effort. If you want, you can be involved there as well.

@ebautistabar
Copy link
Contributor Author

Great. I'll add the changes to the new frontend too. Thanks.

@ebautistabar
Copy link
Contributor Author

As the new UI didn't show job configurations yet, I have created another PR (#953) to deal with it, which also includes the display changes requested in FLINK-2205.

@fhueske
Copy link
Contributor

fhueske commented Aug 3, 2015

This PR is fixing the older UI and still valid, right?
Any reason not to merge it?

@StephanEwen
Copy link
Contributor

I think it is good to merge. The patch for the new UI has already been merged...

@fhueske
Copy link
Contributor

fhueske commented Aug 4, 2015

Merging

@asfgit asfgit closed this in b2d8c40 Aug 4, 2015
@ebautistabar ebautistabar deleted the change-job-config-display branch August 9, 2015 20:30
nikste pushed a commit to nikste/flink that referenced this pull request Sep 29, 2015
…ion.

Default display for 'Number of execution retries' is now 'deactivated'
and for 'Job parallelism' is 'auto', as suggested in JIRA.

This closes apache#927
nltran pushed a commit to nltran/flink that referenced this pull request Jan 8, 2016
…ion.

Default display for 'Number of execution retries' is now 'deactivated'
and for 'Job parallelism' is 'auto', as suggested in JIRA.

This closes apache#927
@coveralls
Copy link

Coverage Status

Changes Unknown when pulling d957523 on ebautistabar:change-job-config-display into ** on apache:master**.

pnowojski pushed a commit that referenced this pull request Jul 3, 2024
…aryTest (#927)

* [FLINKCC-1328] Follow up to add more udf join test cases to QuerySummaryTest
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
6 participants