[jira] [Commented] (NIFI-5239) Make MongoDBControllerService able to act as a configuration source for MongoDB processors

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/NIFI-5239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16599219#comment-16599219 ] 

ASF GitHub Bot commented on NIFI-5239:
--------------------------------------

Github user MikeThomsen commented on the issue:

    https://github.com/apache/nifi/pull/2896
  
    @zenfenan @mattyb149 can one of you review?
    
    The goal here, btw, is to make it so that admins are able to easily share a `MongoClient` between multiple processors. Per the [docs](http://mongodb.github.io/mongo-java-driver/3.5/driver/getting-started/quick-start/#make-a-connection) `MongoClient` is thread-safe and you should limit how many of them your application creates:
    
    > The MongoClient instance represents a pool of connections to the database; you will only need one instance of class MongoClient even with multiple threads.


> Make MongoDBControllerService able to act as a configuration source for MongoDB processors
> ------------------------------------------------------------------------------------------
>
>                 Key: NIFI-5239
>                 URL: https://issues.apache.org/jira/browse/NIFI-5239
>             Project: Apache NiFi
>          Issue Type: New Feature
>            Reporter: Mike Thomsen
>            Assignee: Mike Thomsen
>            Priority: Major
>
> The MongoDBControllerService should be able to provide the getDatabase and getCollection functionality that are built into the MongoDB processors through AbstractMongoDBProcessor. Using the controller service with the processors should be optional in the first release it's added and then mandatory going forward.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)