Erick - tried this, had to run it async, but it's been running for over
24 hours on one collection with:
{
"responseHeader":{
"status":0,
"QTime":18326},
"status":{
"state":"submitted",
"msg":"found [5] in submitted tasks"}}
I don't see anything in the logs.
-Joe
On 3/6/2020 1:43 PM, Joe Obernberger wrote:
Thank you Erick - I have no record of that, but will absolutely give
the API RELOAD a shot! Thank you!
-Joe
On 3/6/2020 10:26 AM, Erick Erickson wrote:
Didn’t we talk about reloading the collections that share the schema
after the schema change via the collections API RELOAD command?
Best,
Erick
On Mar 6, 2020, at 05:34, Joe Obernberger
<joseph.obernber...@gmail.com> wrote:
Hi All - any ideas on this? Anything I can try?
Thank you!
-Joe
On 2/26/2020 9:01 AM, Joe Obernberger wrote:
Hi All - I have several solr collections all with the same schema.
If I add a field to the schema and index it into the collection on
which I added the field, it works fine. However, if I try to add a
document to a different solr collection that contains the new field
(and is using the same schema), I get an error that the field
doesn't exist.
If I restart the cluster, this problem goes away and I can add a
document with the new field to any solr collection that has the
schema. Any work-arounds that don't involve a restart?
Thank you!
-Joe Obernberger
