Shawn Heisey created SOLR-16355:
-----------------------------------
Summary: When there are no changes to commit, an optimize is
skipped
Key: SOLR-16355
URL: https://issues.apache.org/jira/browse/SOLR-16355
Project: Solr
Issue Type: Bug
Security Level: Public (Default Security Level. Issues are Public)
Affects Versions: 9.0
Reporter: Shawn Heisey
I had been trying to run an optimize on my index. Every time I tried it, the
request completed instantly and did not do the optimize.
If I request an optimize while a reindex is underway, so there are uncommitted
changes, then it does actually do the optimize. The index is very small so it
only takes a few seconds.
It looks to me like whatever logic the update handler has which causes a commit
to be a no-op when there are no changes to commit is also causing the optimize
to be a no-op.
This is the request I am making:
{code:java}
curl -v
"http://localhost:8983/solr/dovecot/update?commit=true&optimize=true"{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
