[
https://issues.apache.org/jira/browse/NIFI-4188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16092544#comment-16092544
]
ASF GitHub Bot commented on NIFI-4188:
--------------------------------------
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.
> Create RethinkDB get processor
> ------------------------------
>
> Key: NIFI-4188
> URL: https://issues.apache.org/jira/browse/NIFI-4188
> Project: Apache NiFi
> Issue Type: New Feature
> Components: Extensions
> Affects Versions: 1.3.0
> Environment: All
> Reporter: Mans Singh
> Assignee: Mans Singh
> Priority: Minor
> Labels: document, get, rethinkdb
> Fix For: 1.4.0
>
>
> Create processor for getting documents by id from RethinkDB
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
