[
https://issues.apache.org/jira/browse/CALCITE-1697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16299038#comment-16299038
]
Vladimir Dolzhenko edited comment on CALCITE-1697 at 12/20/17 9:26 PM:
-----------------------------------------------------------------------
No update for a long time.
There is a mongo driver of version 2.14.3 built on 18-Jul-2016, while latest
version is 3.6.0 built on 05-Dec-2017.
There are several deprecated method - especially mongoClient.getDB() and as
consequence have to use Document instead of DBObject.
It is a trade-off to provide compatibility with older version - or force for a
new version ?
+ It is not possible to support authentication mechanism with mongo-driver less
3.0
was (Author: vladimir.dolzhenko):
No update for a long time.
There is a mongo driver of version 2.14.3 built on 18-Jul-2016, while latest
version is 3.6.0 built on 05-Dec-2017.
There are several deprecated method - especially mongoClient.getDB() and as
consequence have to use Document instead of DBObject.
It is a trade-off to provide compatibility with older version - or force for a
new version ?
> Update Mongo driver version
> ---------------------------
>
> Key: CALCITE-1697
> URL: https://issues.apache.org/jira/browse/CALCITE-1697
> Project: Calcite
> Issue Type: Improvement
> Components: mongodb
> Affects Versions: 1.11.0
> Reporter: Michael Mior
> Assignee: Michael Mior
>
> The current version of the Mongo driver is quite outdated. This causes issues
> such as getCollectionNames returning empty on newer versions of the Mongo
> server. This effectively makes the driver unusable since Calcite will never
> see any tables in the schema.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
