Uploaded image for project: 'Jackrabbit Oak'
  1. Jackrabbit Oak
  2. OAK-4400

Correlate index with the index definition used to build it




      Currently, if the definition of an index is changed without reindexing, it will get in an "inconsistent" state.

      Of course, the reindexing is usually necessary, but it would be useful to know with which definition the index was built. This could increase the visibility of the indexing state and help debugging issues related to it.

      Some questions this improvement should respond to:

      1. What is the definition of the index when the (re)indexing was triggered?
      2. Are there any changes in the definition since the trigger? Which?

      I can imagine a solution built by "versioning" the definition nodes (oak:QueryIndexDefinition). When the reindex is triggered, a new version of the node is created and the indexer stores a reference to it.
      This would also allow the indexer to keep using the same definition until a new reindex, even if changes are made meanwhile (i.e. use a fixed version instead of the latest definition).


        1. OAK-4400-v1.diff
          25 kB
          Chetan Mehrotra
        2. OAK-4400-v2.diff
          26 kB
          Chetan Mehrotra
        3. lucene-mbean.png
          51 kB
          Chetan Mehrotra
        4. OAK-4400-v3.diff
          31 kB
          Chetan Mehrotra

          Issue Links



              • Assignee:
                chetanm Chetan Mehrotra
                volteanu Valentin Olteanu
              • Votes:
                1 Vote for this issue
                7 Start watching this issue


                • Created: