Github user alopresto commented on the issue:
https://github.com/apache/nifi/pull/1934
@NielsZeilemaker yes, @jfrazee and I were just talking about that. I think
changing the rejection message to `WARN` is a better solution.
In thinking back, I believe the reason we didn't do that by default is to
prevent log flooding during an attack. If you (an experienced user) set your
threshold for the class to `WARN`, you would not get messages for success or
failure. If you noticed users being rejected, you could temporarily lower the
threshold to diagnose.
But I would be ok with rejection generating a `WARN` message, as in the
positive case (normal operation) that would be far more useful than an admin
missing those messages.
---
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.
---
