[
https://issues.apache.org/jira/browse/NIFI-4124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16064917#comment-16064917
]
ASF GitHub Bot commented on NIFI-4124:
--------------------------------------
Github user bbende commented on a diff in the pull request:
https://github.com/apache/nifi/pull/1945#discussion_r124287931
--- Diff:
nifi-nar-bundles/nifi-mongodb-bundle/nifi-mongodb-processors/pom.xml ---
@@ -48,6 +48,16 @@
</dependency>
<dependency>
<groupId>org.apache.nifi</groupId>
+ <artifactId>nifi-record-serialization-service-api</artifactId>
+ <scope>compile</scope>
--- End diff --
I think you can leave the scope off the record dependencies because you
don't want them actually included in the Mongo NAR... at runtime the Mongo NAR
will have a NAR dependency on standard services NAR which is where the record
dependencies will live.
There is a dependencyManagement block in nifi-nar-bundles pom that sets the
scope to provided, so that may be overriding the scope here anyway, but just
wanted to double check that the record JARs aren't getting bundled into
multiple NARs.
> Add a Record API-based PutMongo clone
> -------------------------------------
>
> Key: NIFI-4124
> URL: https://issues.apache.org/jira/browse/NIFI-4124
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Mike Thomsen
> Priority: Minor
> Labels: mongodb, putmongo, records
>
> A new processor that can use the Record API to put data into Mongo is needed.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
