[
https://issues.apache.org/jira/browse/OAK-6787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16195573#comment-16195573
]
Chetan Mehrotra commented on OAK-6787:
--------------------------------------
bq. I guess that check would happen at the wiring end though, right?
Ack. Would check in LuceneIndexProviderService and configure that in
PropertyIndexCleaner at time of init. PropertyIndexCleaner would have a flag
exposed for recursiveDelete which would be enabled by
LuceneIndexProviderService upon determining the type of NodeStore
> 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)
