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] [Created] (OAK-5212) Avoid updating the index nodestate if no change is done in index
Date Fri, 02 Dec 2016 08:59:58 GMT
Chetan Mehrotra created OAK-5212:
------------------------------------

             Summary: Avoid updating the index nodestate if no change is done in index
                 Key: OAK-5212
                 URL: https://issues.apache.org/jira/browse/OAK-5212
             Project: Jackrabbit Oak
          Issue Type: Improvement
          Components: lucene
            Reporter: Chetan Mehrotra
            Assignee: Chetan Mehrotra
            Priority: Minor
             Fix For: 1.6


As noted in OAK-5211 directory listing was getting modified (due to reorder) even if no change
happens in index. 

Another place where we update state post index close is at ":status" node where we store {{lastUpdated}}
and {{indexedNodes}} post index close. 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. And in doing that IndexWriter
would be initialized.

Currently IndexWriter being initialized is considered same as index updated. Due to this index
status nodes gets unnecessarily updated even if there is no change in index which causes the
IndexTracker to reopen the index even when it has not changed. 

We should make this more explicit and find a way to determine if index has been updated or
not



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

Mime
View raw message