You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Chetan Mehrotra (JIRA)" <ji...@apache.org> on 2015/05/19 08:43:59 UTC
[jira] [Updated] (OAK-2887) Add support for generating mongo export
command to oak-mongo
[ https://issues.apache.org/jira/browse/OAK-2887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chetan Mehrotra updated OAK-2887:
---------------------------------
Attachment: createExportCommand.groovy
attaching [groovy script|^createExportCommand.groovy] which I currently use to create the required exportCommand. We would need to implement possibly similar logic in oak-mongo.js
> Add support for generating mongo export command to oak-mongo
> ------------------------------------------------------------
>
> Key: OAK-2887
> URL: https://issues.apache.org/jira/browse/OAK-2887
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: run
> Reporter: Chetan Mehrotra
> Fix For: 1.3.0
>
> Attachments: createExportCommand.groovy
>
>
> At time to analyse a issue with {{DocumentNodeStore}} running on Mongo we need a dump of various documents so as to recreate the scenario locally. In most case if issue is being observed for a specific path like /a/b then its sufficient to get Mongo documents for /, /a, /a/b and all the split documents for those paths.
> It would be useful to have a function in oak-mongo which generates the required export command. For e.g. for path like /a/b following export command would dump all required info
> {noformat}
> mongoexport -h <mongo server> --port 27017 --db <db name> --collection nodes --out all-required-nodes.json --query '{$or:[{_id : /^4:p\/a\/b\//},{_id : /^3:p\/a\//},{_id : /^2:p\//},{_id:{$in:["2:/a/b","1:/a","0:/"]}}]}'
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)