Github user busbey commented on the issue:
https://github.com/apache/accumulo/pull/151
I don't think this would break Cloudera Manager specifically, since this is
the kind of thing we'd document in Knowledge Base articles for support /
customers rather than try to automate (as mentioned, it's dangerous and a blunt
tool).
But I'd also rather see this in a minor or major release and not a
maintenance release since it changes how an operator facing tool works. I've
already documented / explained / conditioned folks to expect this tool to be
useful in a set of circumstances and to act a certain way (again, since it's
dangerous we train folks to use it by saying what to expect and not expect as
they use it). I won't be able to grab maintenance releases in a
straight-forward way if I have to update internal training things about this
tool to specify different expectations for e.g. 1.7.2 vs 1.7.3.
---
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.
---
