Dear list,
I've experienced a weird (unexpected?) behaviour concerning core reload
on a master instance.
My setup :
master/slave on separate hosts.
On the master, I update the schema.xml file, adding a dynamic field of
type random sort field.
I reload the master using core admin.
The new field is *not* taken into account.
I restart the servlet container (jetty in my case).
The new field is taken into account, I can perform random sort operations.
On the slave side, no problem : at startup the schema.xml replicated,
the core reloaded, and I was able to perform random sorts as well.
Now the question is : what was wrong with the core reload on the master ?
The output it gave to me was something like : "sort param field can't be
found : ${fieldName}".
At this point, in admin/schema view, the schema showing up was indeed
showing the freshly added dynamic field.
I had to restart jetty (not a big issue here, but just to be sure).
Thanks!
--
Tanguy
