Github user jvwing commented on the issue:
https://github.com/apache/nifi/pull/2012
My question about the not_found relationship is not if we should have it or
not -- I think it is a great addition. My question is about the logging for
that code path. You log an error on line 150 when a flowfile is routed to
not_found, and I'm asking if you believe not_found is "bad enough" to deserve
an error. It seems possible that it is a perfectly normal occurrence that keys
are not found in the table, and the flowfile would be routed to not_found
without any worries. As you point out, the user can choose to treat not_found
separately from failure, or not, as they choose. But it is logged as an error
regardless of their choice.
---
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.
---
