Hi, I have an "id" field that is defined on schema.xml with type long. For some use cases the id that is indexed exceeds Max long limitation. I thought about solving it by changing the id to type string.
For my surprise, by only changing the definition on schema.xml and restarting Solr, I was able to read documents and update without the need to re-index. My questions are: 1. Is there another way to overcome the problem except from changing the id to string? 2. Are there any downsides by changing id to string? I know that the schema.xml example comes with id as string by default. 3. I want to avoid full indexing, is it valid just to change the field type? Are there any known issues with this?There's a comment on the example schema about not changing the type, mentioning document routing. This is how the long and string types are defined: <fieldType name="long" class="solr.TrieLongField" precisionStep="0" omitNorms="true" positionIncrementGap="0" sortMissingLast="true" /> <fieldType name="string" class="solr.StrField" sortMissingLast="true" omitNorms="true" /> I'm using Solr Cloud on version 5.2.1. Multiple collections, every collection has only one shard. Thanks,
