[jira] [Updated] (OAK-3087) [oak-mongo.js] Add utility to cleanup hidden structure under disabled indices

["Vikas Saurabh (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/OAK-3087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vikas Saurabh updated OAK-3087:
-------------------------------
    Fix Version/s: 1.6

> [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
>            Assignee: Vikas Saurabh
>            Priority: Minor
>             Fix For: 1.6
>
>         Attachments: 0001-update-removeDescendantsAndSelf-for-upwards-removal.patch, 0002-OAK-3087-Add-some-methods-to-find-disabled-indices-a.patch, cleanupDisbaledIndices-take2.patch, cleanupDisbaledIndices-take3.patch, removeDescendantsAndSelf-api-take2.patch, removeDescendantsAndSelf-api-take3.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)