[
https://issues.apache.org/jira/browse/FLINK-2399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14716430#comment-14716430
]
ASF GitHub Bot commented on FLINK-2399:
---------------------------------------
Github user sachingoel0101 commented on the pull request:
https://github.com/apache/flink/pull/945#issuecomment-135372659
@tillrohrmann , I have modified the way version information is passed to
the Job Manager. It is now through the Configuration object passed.
Further, rolled back on any verification for Job Manager and Task Manager
versions.
There is a possibility to handle compatibility between different versions
by specifying a minimum supported version information. Note that this will
easily be adaptable to Task manager version verification, if needed at some
point.
Let me know if this is a better solution.
> Fail when actor versions don't match
> ------------------------------------
>
> Key: FLINK-2399
> URL: https://issues.apache.org/jira/browse/FLINK-2399
> Project: Flink
> Issue Type: Improvement
> Components: JobManager, TaskManager
> Affects Versions: 0.9, master
> Reporter: Ufuk Celebi
> Assignee: Sachin Goel
> Priority: Minor
> Fix For: 0.10
>
>
> Problem: there can be subtle errors when actors from different Flink versions
> communicate with each other, for example when an old client (e.g. Flink 0.9)
> communicates with a new JobManager (e.g. Flink 0.10-SNAPSHOT).
> We can check that the versions match on first communication between the
> actors and fail if they don't match.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
