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 2017/10/06 06:51:00 UTC

[jira] [Updated] (OAK-6787) Delete property index entries recursively in batches to avoid large transaction

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

Chetan Mehrotra updated OAK-6787:
---------------------------------
    Attachment: OAK-6787-v1.patch

[patch|^OAK-6787-v1.patch] for the same (wiring to cleaner missing)

[~mreutegg] [~catholicon] Please review.

I was thinking to use this when NodeStore is of type Clusterable. wdyt?

> Delete property index entries recursively in batches to avoid large transaction
> -------------------------------------------------------------------------------
>
>                 Key: OAK-6787
>                 URL: https://issues.apache.org/jira/browse/OAK-6787
>             Project: Jackrabbit Oak
>          Issue Type: Technical task
>          Components: lucene
>            Reporter: Chetan Mehrotra
>            Assignee: Chetan Mehrotra
>             Fix For: 1.8
>
>         Attachments: OAK-6787-v1.patch
>
>
> PropertyIndexCleaner currently remove the property index bucket in a single remove. This would work fine with SegmentNodeStore but would cause issue with DocumentNodeStore where it would result in a one large commit.
> To avoid this scenario we should implement recursive delete. This approach would only be used if NodeStore implements Clusterable



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)