[
https://issues.apache.org/jira/browse/FLINK-2425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14651239#comment-14651239
]
ASF GitHub Bot commented on FLINK-2425:
---------------------------------------
Github user StephanEwen commented on the pull request:
https://github.com/apache/flink/pull/952#issuecomment-127077747
I think that silently failing is not a good idea in this case. Silent
failures always keep people wondering why things don't behave like they expect.
It needs to fail with an exception here.
Also, let's make the UnmodifiableConfiguration very lightweight, so that
creating it has little overhead and footprint. Best way to do this is have it
actually wrap the configuration, and have all the "getX()" methods delegate to
the config, while all the "setX()" methods fail with an exception.
> Give access to TaskManager config and hostname in the Runtime Environment
> -------------------------------------------------------------------------
>
> Key: FLINK-2425
> URL: https://issues.apache.org/jira/browse/FLINK-2425
> Project: Flink
> Issue Type: Improvement
> Components: TaskManager
> Affects Versions: 0.10
> Reporter: Stephan Ewen
> Assignee: Sachin Goel
> Fix For: 0.10
>
>
> The RuntimeEnvironment (that is used by the operators to access the context)
> should give access to the TaskManager's configuration, to allow to read
> config values.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
