[
https://issues.apache.org/jira/browse/NIFI-4827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16344213#comment-16344213
]
ASF GitHub Bot commented on NIFI-4827:
--------------------------------------
Github user MikeThomsen commented on a diff in the pull request:
https://github.com/apache/nifi/pull/2443#discussion_r164602408
--- Diff:
nifi-nar-bundles/nifi-mongodb-bundle/nifi-mongodb-processors/src/main/java/org/apache/nifi/processors/mongodb/GetMongo.java
---
@@ -81,6 +82,15 @@ public ValidationResult validate(final String subject,
final String value, final
};
static final Relationship REL_SUCCESS = new
Relationship.Builder().name("success").description("All files are routed to
success").build();
+ static final Relationship REL_FAILURE = new Relationship.Builder()
+ .name("failure")
+ .description("All input flowfiles that are part of a failed
query execution go here.")
--- End diff --
So you're saying it should just be more explicit in the documentation, and
not be some sort of dynamic relationship a la RouteOnAttribute, right?
> Make GetMongo able to use flowfiles for queries
> -----------------------------------------------
>
> Key: NIFI-4827
> URL: https://issues.apache.org/jira/browse/NIFI-4827
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Mike Thomsen
> Assignee: Mike Thomsen
> Priority: Minor
>
> GetMongo should be able to retrieve a valid query from the flowfile content
> or allow the incoming flowfile to provide attributes to power EL statements
> in the Query configuration field. Allowing the body to be used would allow
> GetMongo to be used in a much more generic way.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
