[
https://issues.apache.org/jira/browse/METAMODEL-183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15080913#comment-15080913
]
Xiaomeng Zhao commented on METAMODEL-183:
-----------------------------------------
I want ot work on it:
Mongo -> MongClient, DB ->MongoDatabase.
After check the code, if I do that kind of modification. I will need to modify
the interface of many important classes such as MongoDbDataContext
public MongoDbDataContext(DB mongoDb, SimpleTableDef... tableDefs) _mongoDb
= mongoDb;
_tableDefs = tableDefs;
_schema = null;
}
I need to modify DB to be MongoDatabase. Maybe it will influence MetaModel's
customer's code.
So can I work on this issue or any other solution?
Regards,
Xiaomeng
> 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)
