[
https://issues.apache.org/jira/browse/CAMEL-8668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15314109#comment-15314109
]
Daniel Kulp commented on CAMEL-8668:
------------------------------------
Not to derail this (I won't -1 this), but please make sure this is very very
clear in the docs. There are some big performance regressions in the 3.x
driver series that several of my customers have hit and have decided to stay on
2.x. Some of the regressions are "improving" with the latest 3.2.x, but
still not completely up to 2.x speed. For example, see the discussions on:
https://jira.mongodb.org/browse/JAVA-2110
> Refactoring of Camel-MongoDB based on Java Driver 3.x
> -----------------------------------------------------
>
> Key: CAMEL-8668
> URL: https://issues.apache.org/jira/browse/CAMEL-8668
> Project: Camel
> Issue Type: Improvement
> Components: camel-mongodb
> Reporter: Andrea Cosentino
> Assignee: Arno Noordover
> Priority: Minor
> Fix For: 2.18.0
>
>
> We have updated the MongoDB Java Driver to 3.0.0 version. Everything
> continues to work but there are some new features and best practices to
> modify and implement inside the component. Many classes continues to exist,
> but some of their methods are deprecated and MongoDB recommends to use new
> classes.
> I'd like to work to the adjustment and refactoring of the component, if
> possible.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
