Github user StephanEwen commented on the pull request:
https://github.com/apache/flink/pull/681#issuecomment-103072112
You introduce a separate session ID here. Why not use the JobID as the
session ID? This is how the logic in the JobManager (that attaches the graphs)
currently works. Is there any limitation with that approach that requires to
introduce the new ID?
I am just trying to keep the number of correlated IDs to a minimum here...
---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
