Github user revans2 commented on the pull request:
https://github.com/apache/incubator-storm/pull/168#issuecomment-48752485
As for making this configurable I am fine with that. It just makes means
that if you have that config wrong you will not be able to read any of the data
in ZK. In my testing the CPU utilization did not go up noticeably so I didn't
see much of a reason to make it configurable. The only think I would be
nervous about is if this code is being used for the transactional zookeeper
too. That would mean you would not just have to wipe clean the current state
of the cluster, but also the state of the topologies.
It might be worth it to try and detect if the incoming data is compressed
or not, and only decompress it if it is compressed.
---
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.
---
