-
Notifications
You must be signed in to change notification settings - Fork 188
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MongoDB itest fails on Camel 3.1.0-SNAPSHOT #649
Comments
This is probably related to some changes introduced on master @jamesnetherton was looking at, see #544 |
Yes, I have some WIP locally that'll fix this up. |
@jamesnetherton I think you already noticed but if not, that the quarkus team has added a mongodb driver legacy to our dependencies which should probably be removed once migrating to 3.1 |
@lburgazzoli Actually I think we need to stick with the legacy driver for now. What we really want is for Camel to stop using the deprecated Mongo driver uber-jar, and do like Quarkus in migrating to the newer |
I think we moved away from the old client and we now use the client interface so it should be "simple", @jamesnetherton do you mind having a look as part of #544 ? |
Yep, that's one part of it - but camel-mongodb still uses other deprecated APIs which require the presence of the legacy driver dependency. |
uff |
wonder if we should remove them, maybe add some deprecation on 3.0.x if needed |
I think its mostly internal usage for the component, so probably no need for deprecation. It'd be good if the component could move to the newer driver in 3.1.x. |
I raised CAMEL-14423. It's not a hard dependency for resolving this issue or #544. For now, we can live with including the legacy driver until the component moves to using the updated APIs. |
Turns out we do have a incompatibility issue 😞 . I thought Quarkus had bumped to the latest version of the Mongo driver, but they are still on 3.10.x, which is not compatible with 3.12.x used in Camel 3.1.0. It seems fixable with some dependency overrides on our side. Otherwise we need quarkusio/quarkus#6347 merged for Quarkus 1.2.0.Final. |
Fixed in d68e8b7. |
Reproducible against the code in #651
The log:
The text was updated successfully, but these errors were encountered: