[
https://issues.apache.org/jira/browse/METAMODEL-183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15088879#comment-15088879
]
ASF GitHub Bot commented on METAMODEL-183:
------------------------------------------
GitHub user xmpy opened a pull request:
https://github.com/apache/metamodel/pull/86
METAMODEL-183: Upgrad MongoDB API and seperate MongoDB module into mon…
Take over @loorenzooo 's work. Thank you very much.
Besides loorenzooo's work, I also do following works:
1. Seperate the mongo module into mongo2 and mongo3
This work follows the discussion in this mail:
https://mail-archives.apache.org/mod_mbox/metamodel-dev/201511.mbox/%3ccakxzecgvsuunrhye9ahbcb_hz5gh3rnqhbhvuesx4f3dyxd...@mail.gmail.com%3E
metamodel
.......
|-- mongodb
|-- commons
|-- mongo2
|-- mongo3
2. replace all the DBObject by Document and DBObjectList by List<Document>
3. Enable write concern in mongo3 module
4. close MongoClient to escape warnings
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/xmpy/metamodel xmpy_upgrade_mongodb_api
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/metamodel/pull/86.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #86
----
commit 73a770ceefef4c8512e9d58612fb2a5dd0aa324f
Author: zhaoxm <[email protected]>
Date: 2016-01-08T08:12:13Z
METAMODEL-183:Upgrad MongoDB API and seperate MongoDB module into mongo2
and mongo3
----
> 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)
