Github user attachmentgenie commented on the issue:
https://github.com/apache/flink/pull/2680
@uce i made the changes are requested. With a few slight modifications
however.
1.
`.defaultValue(null);` throws an error so i opted to use
`.noDefaultValue();` which behaves
Github user attachmentgenie commented on the issue:
https://github.com/apache/flink/pull/2680
@uce i personally always prefer a explicit default as that keeps me in
control instead of the upstream implementation, but i can live with setting it
to `null`.
---
If your project is set
Github user attachmentgenie commented on the issue:
https://github.com/apache/flink/pull/2680
@StephanEwen seems reasonable thing to do, i updated the code to use the
new ConfigOption method
---
If your project is set up for it, you can reply to this email and have your
reply appear
GitHub user attachmentgenie opened a pull request:
https://github.com/apache/flink/pull/2680
[FLINK-4876] Allow web interface to be bound to a specific
ip/interface/inetHost
Currently the web interface automatically binds to all interfaces on
0.0.0.0. IMHO there are some use cases
