Uploaded image for project: 'Jackrabbit Content Repository'
  1. Jackrabbit Content Repository
  2. JCR-3905

Journal sync after full re-index does not save journal revision

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 2.8.1
    • Fix Version/s: None
    • Labels:
      None
    • Environment:
      SQL persistence store

      Description

      In org.apache.jackrabbit.core.query.lucene.SearchIndex.doInit, if it discovers that the index is empty, it creates an initial index and then calls checkPendingJournalChanges(). That method reads all the new journal records (all at once, which is separate bug JCR-2483) and applies them. Since it is now caught up, it should save the revision number that it is up to, but it appears not to. As far as I can tell, this means that when the next journal sync occurs, it will re-fetch and re-process all the records it just processed.
      Also, it's not clear why it bothers to process the journal at this stage anyway, instead of letting it happen at the next journal sync.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                pwasson Philip Wasson
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated: