Github user StephanEwen commented on the pull request:
https://github.com/apache/flink/pull/945#issuecomment-125886476
Using `getClass().getPackage().getImplementationVersion()` would be a
decent first approach then, I guess. The critical part seems to be the
Client-to-JobManager communication.
How about the following as a first step: The client sends its version
together with the `SubmitJob` message (just add a field there). The JobManager
would check the version and respond with a failure, if it does not match. You
can probably make the JobManager part very simple, no need to add extra
constructor parameters, etc.
That way, the change would be minimally invasive, and we could see how well
it addresses the issues, and whether we should extend this to other messages as
well.
---
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.
---
