[
https://issues.apache.org/jira/browse/FLINK-2399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14713074#comment-14713074
]
ASF GitHub Bot commented on FLINK-2399:
---------------------------------------
Github user tillrohrmann commented on a diff in the pull request:
https://github.com/apache/flink/pull/945#discussion_r37978132
--- Diff:
flink-core/src/main/java/org/apache/flink/configuration/Configuration.java ---
@@ -54,8 +54,12 @@
/** Stores the concrete key/value pairs of this configuration object. */
- private final HashMap<String, Object> confData;
-
+ private final Map<String, Object> confData;
+
+ /** Stores the program version */
+ public final String FLINK_VERSION =
getClass().getPackage().getImplementationVersion() ==
+ null ? "FLINK_TEST_VERSION" :
getClass().getPackage().getImplementationVersion();
--- End diff --
What's the value of `FLINK_VERSION` if you execute a Flink job on a
standalone cluster from your IDE using the `RemoteExecutionEnvironment`? Will
it work?
> 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)
