Apache Solr open-source search software
SOLR-16397: Fix warning in merge-indices docs
Jason Gerlowski23dd73877f48
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.adocindex 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 untThe 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 cocurl -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 mayAlternatively, 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 APcurl -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]