[
https://issues.apache.org/jira/browse/OAK-424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13493261#comment-13493261
]
Michael Dürig commented on OAK-424:
-----------------------------------
I get test failures when I run {{mvn clean install -Pmongomk}} do I need to
have a local MongoDB instance running in order for this to work or should it
work OOTB?
> MongoMicroKernel changes
> ------------------------
>
> Key: OAK-424
> URL: https://issues.apache.org/jira/browse/OAK-424
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: mk
> Reporter: Mete Atamel
> Attachments: oak-mongomk-merge-failure-test.diff
>
>
> I worked on MongoMK in my own fork [0] and this is a request to merge those
> changes back into Oak. There's a pull request [1] but the summary of changes
> are the following:
> -Performance tests for MicroKernel by Tudor Rogoz.
> -Test and fix for OAK-351
> -Removed all @author and other code reorganization
> -Fix for FetchValidCommitsQuery
> -Fix for MicroKernelIT#copyDescendant test
> -Jsop fixes
> -Diff support and tests
> -Osgi support
> -Branch support and tests
> -Merge support and tests
> -GetJournal fixes
> -GetRevisionHistory fixes
> -Fixes and tests for copy, move nodes
> -Fix for OAK-384
> -General API and code cleanup
> -Split diff, merge, getJournal, getRevHistory, waitForCommit into its own
> commands
> -Converted *CommandMongo tests into MongoMK* tests
> -Fixes for concurrency issue reported by Tudor.
> -Renamed head collection to sync
> -Moved MongoUtil functionality under Mongoconnection
> -Renamed *Query clases into *Action
> -oak-mongo-perf cleanup
> -Merged CommitImpl into CommitMongo
> -Renamed MongoBlobStore to MongoGridFSBlobStore
> -Initial MongoBlobStore implementation based on AbstractBlobStore
> -Blob retrieval fix in MongoGridFSBlobStore
> -Move collection handling from MongoConnection to MongoNodeStore
> [0] https://github.com/meteatamel/jackrabbit-oak/
> [1] https://github.com/apache/jackrabbit-oak/pull/6
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
