Not a dissimilar issue, I'm receiving "Field type 'solr.TextField' not found" when I try
curl --request POST \ --url http://localhost:8983/api/collections/minervasus/schema \ --header 'Content-Type: application/json' \ --data '{ "add-field": [ {"name": "tester", "type": "solr.LongPointField", "multiValued": false, "required": true} ] }' Which looks like the file schema_extra_types.xml hasn't been installed as a part of the download/unpack/run of solr9.1.1 per here https://solr.apache.org/guide/solr/latest/getting-started/solr-tutorial.html Did you find a fix? Regards Tim On 2023/03/16 08:24:05 Björn Häuser wrote: > Hello Solr users, > > We are currently in the process of moving from Trie* classes away and are having some questions how todo the migration. > During that we are having some questions, where we cannot find an answer in the documentation. > > 1.) Are these equivalent field definitions? > > Old: > > <fieldType name="long" class="solr.TrieLongField" precisionStep="0" positionIncrementGap="0”/> > > New: > > <fieldType name="long" class="solr.LongPointField" docValues="true”/> > > I cannot find anything about precisionStep and positionIncrementGap for the new fields and assume that docValues will take care of that in some way? > > 2.) Do we need to reindex after the scheme change? > > We have a large collections and are serving requests 24/7. Is a full index required or is Solr/Lucene able to handle both field types until everything is updated? > > > Thank you > Björn > >
