Github user mcgilman commented on the issue:
https://github.com/apache/nifi/pull/726
@joewitt I'm still seeing a bunch of details in error messages coming back
to the client. Specifically what I'm seeing right now, it looks like
StandardProcessGroup is using the toString of it's encapsulated components when
generating exception message. We should ensure these toString's don't include
those details.
You should be able to see examples of some of these by issuing requests
that are invalid. Like deleting a component that has an incoming connection,
deleting a group in an invalid state (when data is enqueued in an encapsulated
connection), etc.
---
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.
---
