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] [Resolved] (OAK-5211) OakDirectory should not save dir listing if no change is done
Date Fri, 02 Dec 2016 08:48:58 GMT

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

Chetan Mehrotra resolved OAK-5211.
       Resolution: Fixed
    Fix Version/s: 1.5.15

Done with 1772311

> OakDirectory should not save dir listing if no change is done
> -------------------------------------------------------------
>                 Key: OAK-5211
>                 URL: https://issues.apache.org/jira/browse/OAK-5211
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: lucene
>            Reporter: Chetan Mehrotra
>            Assignee: Chetan Mehrotra
>            Priority: Minor
>              Labels: performance
>             Fix For: 1.6, 1.5.15
> [~alex.parvulescu] noted that OakDirectory saves the directory listing even if no actual
change happened in the directory. Only change that happens is the order of entries in set.

> In normal cases LuceneIndexEditor avoids initializing the IndexWriter if there is no
change. However it can happen that when any node gets deleted the editor performs a delete
operation. It can happen that tree being deleted is not indexed but still editor would do
this as it cannot determine that easily. This would lead to OakDirectory being closed without
any change and thus can lead save of dir listing with just change in order of entries

This message was sent by Atlassian JIRA

View raw message