Github user cestella commented on the issue:
https://github.com/apache/metron/pull/717
@merrimanr Thanks for mentioning num workers. I just missed it when going
through; I intended to add all relevant things to override, so I'm going to add
num workers and num ackers too. I'll add them now.
The intent of the use of suppliers here is to keep the logic for parameter
overrides in the CLI without needing the CLI to necessarily have to know how to
pull in the sensor parser configs (we currently keep that functionality in the
ParserTopology class. I believe this separation of concerns has some value, so
I wanted to provide a way where we could keep the logic in the CLI without
having to interact with zookeeper and move logic around, thus moving from
"here's the value" to "here's a way to get the value" type semantics. I could
see how that might be confusing since it's creating some indirection where
there was no indirection before. Perhaps I can add some comments to that
effect justifying the reasons and it'll be clearer?
---
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.
---
