Github user arunmahadevan commented on the pull request:
https://github.com/apache/storm/pull/1199#issuecomment-196684996
@knusbaum @ptgoetz in the proposed name based approach, the naming needs to
be done only when one wants to pass specific configs to the node executing the
streaming operation, not always. Agree it has magic strings which needs to be
matched, but it keeps the configuration and streaming operations separate. The
main concern with adding the apis to the Stream is that as we add new config
apis to the stream, the stream api gets messy.
Understand the current limitations, so for now I think we may make it as a
part of the stream api, but do evaluate directly adding all the methods to the
stream vs adding a single config method taking params.
---
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.
---
