(jackrabbit-oak) branch OAK-11729 updated: OAK-11729: If the indexing lane is behind, we should allow catch up of a non-failing lane

[mkataria]

This is an automated email from the ASF dual-hosted git repository.

mkataria pushed a commit to branch OAK-11729
in repository https://gitbox.apache.org/repos/asf/jackrabbit-oak.git


The following commit(s) were added to refs/heads/OAK-11729 by this push:
     new fc8a388715 OAK-11729: If the indexing lane is behind, we should allow 
catch up of a non-failing lane
fc8a388715 is described below

commit fc8a388715978ac8cad9eca16ae7ca16bf3eae01
Author: Mohit Kataria <tiho...@gmail.com>
AuthorDate: Mon Jul 21 15:50:57 2025 +0530

    OAK-11729: If the indexing lane is behind, we should allow catch up of a 
non-failing lane
---
 .../apache/jackrabbit/oak/plugins/index/AsyncIndexUpdateTest.java    | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git 
a/oak-core/src/test/java/org/apache/jackrabbit/oak/plugins/index/AsyncIndexUpdateTest.java
 
b/oak-core/src/test/java/org/apache/jackrabbit/oak/plugins/index/AsyncIndexUpdateTest.java
index 55f5d59fb0..825680c09d 100644
--- 
a/oak-core/src/test/java/org/apache/jackrabbit/oak/plugins/index/AsyncIndexUpdateTest.java
+++ 
b/oak-core/src/test/java/org/apache/jackrabbit/oak/plugins/index/AsyncIndexUpdateTest.java
@@ -621,7 +621,7 @@ public class AsyncIndexUpdateTest {
         assertEquals(Set.of("testRoot", "testRoot1"), find(lookup, "foo", 
"abc"));
 
         // Index catchup should work even if the async lane is not failing. 
Refer: https://issues.apache.org/jira/browse/OAK-11729
-        // So changing lane will skip indexing this node.
+        // So force catchup will skip indexing this node.
         builder.child("testRoot2").setProperty("foo", "abc");
         store.merge(builder, EmptyHook.INSTANCE, CommitInfo.EMPTY);
         async.getIndexStats().forceIndexLaneCatchup("CONFIRM");
@@ -653,7 +653,8 @@ public class AsyncIndexUpdateTest {
         assertFalse(root.getChildNode(INDEX_DEFINITIONS_NAME).hasChildNode(
                 ":conflict"));
         lookup = new PropertyIndexLookup(root);
-        // both testRoot2 and testRoot3 will not be indexed, because these 
were created after the last successfully run index update and before the 
forceUpdate.
+        // both testRoot2 and testRoot3 will not be indexed, because these 
were created after the last successfully run
+        // index update and before the force catchup.
         // So it lands in the missing content diff that needs to be reindexed.
         assertEquals(Set.of("testRoot", "testRoot1", "testRoot4"), 
find(lookup, "foo", "abc"));
         // Check if failing index update is fixed