Github user fhueske commented on the pull request:
https://github.com/apache/flink/pull/1046#issuecomment-140222747
Actually, I think going through the `TaskConfig` as proposed by @mjsax is
the cleaner way. Going through the system-internal `JobConfiguration` and
exposing it to user programs is not a good choice, in my opinion.
The purpose of `TaskConfig` is exactly to give parameters to a task
(function, spout). Also the `StreamingRuntimeContext` would not need to be
adapted, because it already offers a method `getTaskStubParameters()`. Would
that work as well or are there major issues preventing you from using the
`TaskConfig`?
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
