metamodel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (METAMODEL-183) For Mongo DB model, use new APIs instead of old ones.
Date Tue, 12 Jan 2016 14:28:39 GMT

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

ASF GitHub Bot commented on METAMODEL-183:
------------------------------------------

Github user xmpy commented on the pull request:

    https://github.com/apache/metamodel/pull/86#issuecomment-170926968
  
    I still have a little concern about org.apache.metamodel.DataContextFactory, in this factory,
we return the mongo2 MongoDataContext. In the pom of this `full` maven project, we add both
`MetaModel-mongodb-mongo2` and `MetaModel-mongodb-mongo3` dependency, but they rely on different
version of mongdb driver. It will lead maven package collide. To my best know, the final jar
will include the mongodb driver with newest version. Is it right?  :)


> For Mongo DB model, use new APIs instead of old ones.
> -----------------------------------------------------
>
>                 Key: METAMODEL-183
>                 URL: https://issues.apache.org/jira/browse/METAMODEL-183
>             Project: Apache MetaModel
>          Issue Type: Improvement
>            Reporter: Hosur Narahari
>            Priority: Minor
>
> I observed that we are using old APIs of MongoDB in our metamodel project, like Mongo
instead of MongoClient, DB instead of MongoDatabase and many more. It would be better if we
replace this with new API as support for Mongo driver would be for the new one.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message