You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Pierre Villard (JIRA)" <ji...@apache.org> on 2017/08/16 17:23:00 UTC
[jira] [Resolved] (NIFI-1986) Expression Language not supported for
Mongo Collection Names
[ https://issues.apache.org/jira/browse/NIFI-1986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pierre Villard resolved NIFI-1986.
----------------------------------
Resolution: Duplicate
> Expression Language not supported for Mongo Collection Names
> ------------------------------------------------------------
>
> Key: NIFI-1986
> URL: https://issues.apache.org/jira/browse/NIFI-1986
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework
> Affects Versions: 0.6.1
> Reporter: jon schendt
> Priority: Minor
> Labels: mongodb, nifi, putmongo
> Original Estimate: 4h
> Remaining Estimate: 4h
>
> When creating a workflow to insert data into Mongo, I have many data flows running into the PutMongo processor. I would like to insert these records into collections that show their data source via an attribute. The PutMongo processor (which is driven by AbstractMongoProcessor) doesn't allow for dynamic collection assignment via expression language. The workaround is having 1..n PutMongo processors, all pointing to the same DB, with different collection names assigned for each workflow. This seems very un-Nifi, and appears to be fairly simple to modify the AbstractMongoProcessor to allow expressions.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)