Github user ottobackwards commented on the issue:
https://github.com/apache/incubator-metron/pull/338
You can solve this problem ( and the grok problem ) without storing the
world in ZK with tooling. An official set of scripts/web interface for
deploying scripts/topologies/grok rules to whatever location. This tooling can
change the version, checksum, crc whatever in the configurations in ZK and
trigger the reload from disk.
I don't know what the real benefit from storing the scripts or rules in ZK
are beyond notification. It seems to me to make things harder.
If there is no other reason, and it is only for triggering change maybe a
tool/flag approach would be simpler?
---
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.
---
