Github user asfgit closed the pull request at:
https://github.com/apache/flink/pull/1185
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enab
Github user StephanEwen commented on the pull request:
https://github.com/apache/flink/pull/1185#issuecomment-144012726
Merging this...
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this fe
Github user StephanEwen commented on the pull request:
https://github.com/apache/flink/pull/1185#issuecomment-143713277
+1, looks good.
I think the ports / URLs were in there, because originally we had two
backend servers running (the old one and the new one) while gradually
Github user aljoscha commented on the pull request:
https://github.com/apache/flink/pull/1185#issuecomment-143687678
+1
I built it and ran it on a custom port, data seems to be displayed
correctly
---
If your project is set up for it, you can reply to this email and have your
re
Github user rmetzger commented on the pull request:
https://github.com/apache/flink/pull/1185#issuecomment-143433645
Remember to assign the JIRA to yourself ;)
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your proje
GitHub user uce opened a pull request:
https://github.com/apache/flink/pull/1185
[FLINK-2769] [dashboard] Remove hard coded job server URL
Removes the hard coded job server URL for the client scripts. This was
preventing the web server port configuration to be picked up by the clien
