On 12/21/22 04:38, Sergio García Maroto wrote:
Hi Shawn. Thanks again for your help
I fixed the url and now i can see the collectionprops.json with the new
field under /collections/person/collectionprops.json .
I have now two properties just for testing.
{
"savefields":"false",
"save.fields":"false"
}
Here my schema field again
<field name="SmartSearchS" type="SmartSearchField" indexed="true" stored=
"${savefields:true}" multiValued="true" />
I created the "save.fields" property and set it to "true" and added this
to my schema:
<field name="test" type="string" indexed="false"
stored="${save.fields:bleh}"/>
This did not throw an error on startup which I would expect if the
property were not available. A document indexed with the test field
does show the field in the result.
Then I added another field:
<field name="test2" ype="string" indexed="false"
stored="${not.defined:bleh}"/>
I did not create the "not.defined" property, and Solr did throw an error
as soon as I uploaded the new config to zookeeper because it tried to
use "bleh" which the schema class doesn't understand.
Are you absolutely sure that you reindexed the document you checked?
Changing the schema in this way will not affect documents that were
indexed before the change. You might want to completely delete the
index directory before your next reload/restart and then reindex, just
to be absolutely sure there is no data from the old schema.
Are you uploading the changed config to zookeeper? In cloud mode Solr
does not use any config on disk.
Thanks,
Shawn
