This is an automated email from the ASF dual-hosted git repository.
epugh pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/solr.git
The following commit(s) were added to refs/heads/main by this push:
new dd1ed4b711c Fix formatting of commit and optimize operation tags
(#4740)
dd1ed4b711c is described below
commit dd1ed4b711c869e89428fc01e76fbba8676359fc
Author: Eric Pugh <[email protected]>
AuthorDate: Sat Aug 15 14:11:37 2026 -0400
Fix formatting of commit and optimize operation tags (#4740)
---
.../modules/indexing-guide/pages/indexing-with-update-handlers.adoc | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
a/solr/solr-ref-guide/modules/indexing-guide/pages/indexing-with-update-handlers.adoc
b/solr/solr-ref-guide/modules/indexing-guide/pages/indexing-with-update-handlers.adoc
index 68a5ede4935..5f891e8dd41 100644
---
a/solr/solr-ref-guide/modules/indexing-guide/pages/indexing-with-update-handlers.adoc
+++
b/solr/solr-ref-guide/modules/indexing-guide/pages/indexing-with-update-handlers.adoc
@@ -135,7 +135,7 @@ Blocks until a new searcher is opened and registered as the
main query searcher,
+
Merges segments that have more than 10% deleted docs, expunging the deleted
documents in the process.
Resulting segments will respect `maxMergedSegmentMB`.
-This option only applies in a `<commit> operation`.
+This option only applies in a `<commit>` operation.
+
WARNING: `expungeDeletes` is less expensive than optimize, but the same
warnings apply.
@@ -148,7 +148,7 @@ WARNING: `expungeDeletes` is less expensive than optimize,
but the same warnings
+
Makes a best effort attempt to merge the segments down to no more than this
number of segments but does not guarantee that the goal will be achieved.
Unless there is tangible evidence that optimizing to a small number of
segments is beneficial, this parameter should be omitted and the default
behavior accepted.
-This option only applies in a `<optimize` operation.
+This option only applies in a `<optimize>` operation.
Default is unlimited, resulting segments respect the `maxMergedSegmentMB`
setting.
Here are examples of `<commit>` and `<optimize>` using optional attributes:
