99.9% sure that if you look closely, you’ll find that these fields are
inappropriately defined. What may have happened is that there are tighter
checks in Solr 8 that throw errors where the contradictory definitions were
silently ignored. For instance you report one error:
SORTED_NUMERIC to SO
Hi Shawn,
Thanks for your reply.
The core is used to test the solr setup by creating a trial collection. But
other than that every collection created are exactly the same as existing
one. I don't think this would create a problem, please brief me if it is
otherwise.
Thanks and regards,
Bhuvanesh
On 9/16/2019 10:18 AM, Bhuvanesh wrote:
Recently I created a cloud Solr 8.1.1 with zookeeper similar to cloud Solr
6.6.2 which is in use. All configurations and schema files are exactly
alike, but when I try to index the same documents Solr throws *cannot
change field "FIELD_NAME" from* *index op
Hi team,
Recently I created a cloud Solr 8.1.1 with zookeeper similar to cloud Solr
6.6.2 which is in use. All configurations and schema files are exactly
alike, but when I try to index the same documents Solr throws *cannot
change field "FIELD_NAME" from* *index options=DOCS_AND_FREQS_AND_POSITIO
