Github user ctubbsii commented on the issue:
https://github.com/apache/accumulo/pull/242
I think the data model in the classes could be improved/refactored a bit,
but it's the REST API we want to make consumable, not the internal
implementation. I don't think it matters whether these POJO fields are private
with getters, or public, or whether there's a hierarchy of POJOs vs. custom
classes with named fields. It would be nice to clean up all of them so that
there is some consistency, and a lot of simplicity, but I don't think we should
expect these internal classes representing the REST data model to be publicly
consumable.
---
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.
---
