(solr) branch branch_9x updated: SOLR-16397: Fix warning in merge-indices docs

[ge...@apache.org]

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

gerlowskija pushed a commit to branch branch_9x
in repository https://gitbox.apache.org/repos/asf/solr.git


The following commit(s) were added to refs/heads/branch_9x by this push:
     new 3c05af51032 SOLR-16397: Fix warning in merge-indices docs
3c05af51032 is described below

commit 3c05af51032521c36c4d0ccecec086ee26f03bf8
Author: Jason Gerlowski <ge...@apache.org>
AuthorDate: Mon Jan 22 14:42:53 2024 -0500

    SOLR-16397: Fix warning in merge-indices docs
---
 .../modules/configuration-guide/pages/coreadmin-api.adoc          | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/solr/solr-ref-guide/modules/configuration-guide/pages/coreadmin-api.adoc b/solr/solr-ref-guide/modules/configuration-guide/pages/coreadmin-api.adoc
index 173d4e4ee4b..9daedadf701 100644
--- a/solr/solr-ref-guide/modules/configuration-guide/pages/coreadmin-api.adoc
+++ b/solr/solr-ref-guide/modules/configuration-guide/pages/coreadmin-api.adoc
@@ -574,7 +574,7 @@ The indexes must have completed commits, and should be locked against writes unt
 The target core index must already exist and have a compatible schema with the one or more indexes that will be merged to it.
 Another commit on the target core should also be performed after the merge is complete.
 --
-[example.tab-pane#v1coreadmin-mergeindexes]
+[example.tab-pane#v1coreadmin-mergeindexes-dir]
 ====
 [.tab-label]*V1 API*
 [source,bash]
@@ -582,7 +582,7 @@ Another commit on the target core should also be performed after the merge is co
 curl -X GET "http://localhost:8983/solr/admin/cores?action=MERGEINDEXES&core=targetCoreName&indexDir=path/to/core1/data/index&indexDir=path/to/core2/data/index"
 ----
 ====
-[example.tab-pane#v2coreadmin-mergeindexes]
+[example.tab-pane#v2coreadmin-mergeindexes-dir]
 ====
 [.tab-label]*V2 API*
 [source,bash]
@@ -602,7 +602,7 @@ A benefit of this approach is that we can merge any Lucene-based index that may
 
 Alternatively, we can instead use a `srcCore` parameter (`srcCores` in the v2 API), as in the example below:
 --
-[example.tab-pane#v1coreadmin-mergeindexes]
+[example.tab-pane#v1coreadmin-mergeindexes-core]
 ====
 [.tab-label]*V1 API*
 [source,bash]
@@ -610,7 +610,7 @@ Alternatively, we can instead use a `srcCore` parameter (`srcCores` in the v2 AP
 curl -X GET "http://localhost:8983/solr/admin/cores?action=mergeindexes&core=targetCoreName&srcCore=core1&srcCore=core2"
 ----
 ====
-[example.tab-pane#v2coreadmin-mergeindexes]
+[example.tab-pane#v2coreadmin-mergeindexes-core]
 ====
 [.tab-label]*V2 API*
 [source,bash]