jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chetan Mehrotra (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-3087) [oak-mongo.js] Add utility to cleanup hidden structure under disabled indices
Date Thu, 09 Jul 2015 05:40:04 GMT

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

Chetan Mehrotra commented on OAK-3087:
--------------------------------------

bq. update the API to accept a maxDepth parameter and then delete upwards from that depth

May be we make that as default i.e. upward. For that we need to define the maxDepth. That
I think we can do with a call to mongo with increasing depth and using findOne untill you
get a null response. That would then constitute as maxDepth



> [oak-mongo.js] Add utility to cleanup hidden structure under disabled indices
> -----------------------------------------------------------------------------
>
>                 Key: OAK-3087
>                 URL: https://issues.apache.org/jira/browse/OAK-3087
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: mongomk
>            Reporter: Vikas Saurabh
>            Priority: Minor
>         Attachments: 0001-update-removeDescendantsAndSelf-for-upwards-removal.patch,
0002-OAK-3087-Add-some-methods-to-find-disabled-indices-a.patch
>
>
> While disabling property indices, avoids usage of those indices. But, they still maintain
the data already stored under them. That data would keep on consuming storage space without
serving any purpose. Also, it'd pile on mongo's id index.
> While one can delete index definition node to clear these nodes up -- but, it'd be really
slow and a JCR based deleted would first create a HUGE commit while marking all documents
under it as deleted. And, then the actual deletion would happen in next revision GC after
24 hours have past.
> Hence, it might be beneficial to have a low level api in oak-mongo.js, which simply removes
the document from mongo altogether.



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

Mime
View raw message