Github user StephanEwen commented on the issue:
https://github.com/apache/flink/pull/5530
I think this looks quite good now.
Since 1.5 feature freeze is over for a bit, would suggest to merge this
into master (1.6-SNAPSHOT).
Looking at the code (this PR and the high a
Github user tillrohrmann commented on the issue:
https://github.com/apache/flink/pull/5530
You could rebase on the latest master and force push to retrigger the build.
---
Github user kbialek commented on the issue:
https://github.com/apache/flink/pull/5530
Looks like build process was terminated by kernel. Can someone retrigger it?
---
Github user kbialek commented on the issue:
https://github.com/apache/flink/pull/5530
Now uses high-availability configuration property can be set either to
none, zookeeper or FQN of factory class
---
Github user kbialek commented on the issue:
https://github.com/apache/flink/pull/5530
Closing without merge, because of:
1. Test failure
2. I'd like to implement Stephan's idea
---
Github user StephanEwen commented on the issue:
https://github.com/apache/flink/pull/5530
I think this is a nice approach.
I would suggest to not split the config options between `high-availability`
and factory that is only used in *CUSTOM* mode, but use the `high-availability
