[ 
https://issues.apache.org/jira/browse/CAMEL-14258?focusedWorklogId=358789&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-358789
 ]

ASF GitHub Bot logged work on CAMEL-14258:
------------------------------------------

                Author: ASF GitHub Bot
            Created on: 12/Dec/19 16:43
            Start Date: 12/Dec/19 16:43
    Worklog Time Spent: 10m 
      Work Description: squakez commented on pull request #3405: CAMEL-14258: 
switching old MongoClient to new interface
URL: https://github.com/apache/camel/pull/3405
 
 
   
   * switching com.mongodb.MongoClient to com.mongodb.client.MongoClient
   * Adding support for explicit WriteConcern and ReadPreferences
   * Updated unit test to fit new client
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


Issue Time Tracking
-------------------

            Worklog Id:     (was: 358789)
    Remaining Estimate: 0h
            Time Spent: 10m

> [camel-mongodb] New MongoClient driver recommendations
> ------------------------------------------------------
>
>                 Key: CAMEL-14258
>                 URL: https://issues.apache.org/jira/browse/CAMEL-14258
>             Project: Camel
>          Issue Type: Improvement
>            Reporter: Pasquale Congiusti
>            Assignee: Pasquale Congiusti
>            Priority: Minor
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Starting from version mongo-java-driver 3.7 version, the recommended way to 
> create a connection to MongoDB is using the [MongoClients 
> factory|https://mongodb.github.io/mongo-java-driver/3.7/javadoc/?com/mongodb/client/MongoClient.html]
>  which is finally returning a _com.mongodb.client.MongoClient_.
> We're originally using _com.mongodb.MongoClient_ class instead, so we should 
> switch to the new implementation to be aligned with the latest recommendation.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to