prevent DOCS_AND_FREQS_AND_POSITIONS Solr error #11140
Conversation
pdurbin
added
Size: 3
|
W.r.t. release notes, hopefully the Solr 9.7.0 update gets into 6.6 which would avoid people having to do this? |
|
@qqmyers I had that thought. Yes, that will also fix it. But I also wanted to write down the bug and fix. Definitely if we tell people to upgrade to a new version of Solr we won't need the extra steps in this PR. |
|
Good addition. I can confirm that emptying the Solr index before reloading the schema fixes that error message. |
On internal I ended up erasing the index and reindexing from scratch. |
| ```shell | ||
| curl "http://localhost:8983/solr/admin/cores?action=RELOAD&core=collection1" | ||
| ``` | ||
|
|
There was a problem hiding this comment.
The above will work just fine.
But it may be even simpler to tell them to clear the existing index before updating the schema (in step 7., before stopping solr). Since changing the schema requires stopping and restarting, no need to reload the core as a separate step.
Just a thought - up to you; not a big deal either way.
What this PR does / why we need it:
This PR updates the release note added for #10887 to prevent a strange "DOCS_AND_FREQS_AND_POSITIONS" error we observed switching to the Solr schema.xml in that PR.
Which issue(s) this PR closes:
Special notes for your reviewer:
Suggestions on how to test this:
Two ways:
Try to reproduce #11139 on a classic installation where we've kept the Solr index (internal or beta, maybe?). [edit: not internal - I erased the old index there before reindexing - L.A.]
In a Docker environment run code prior to #10887 (consider running the search tests with
mvn test -Dtest=SearchIT). Then pull the latest to pick up #10887, upgrade your schema withcp conf/solr/schema.xml docker-dev-volumes/solr/data/data/collection1/conf/schema.xml, and then try to reproduce #11139.Does this PR introduce a user interface change? If mockups are available, please link/include them here:
No.
Is there a release notes update needed for this change?:
Yes, this PR updates release notes.
Additional documentation:
None.