: > whoa... that's not normal .. what *exactly* does the fieldType declaration : > (with all analyzers) look like, and what does the <field/> declaration : > look like? : > : > : <field name="debtor_id" type="text_general" multiValued="false" : indexed="true" required="true" stored="true"/> : : <fieldType name="text_gen_sort" class="solr.SortableTextField" : positionIncrementGap="100" multiValued="true">
NOTE: "text_general" != "text_gen_sort" Assuming your "text_general" declaration looks like it does in the _default config set, then using that for uniqueKey or sorting is definitly not a good idea. If you were *actually* using SortableTextField for your uniqueKeyField ... well, that should be ok to *sort* on, but i still wouldn't suggest using it as a uniqueKey field ... honestly not sure what behavior that might have with things like deleteById, etc... : I am going to adjust my schema, re-index, and try again. See if that : doesn't fix this problem. I didn't know that having the uniqueKey be a : textField was a bad idea. https://lucene.apache.org/solr/guide/8_3/other-schema-elements.html#OtherSchemaElements-UniqueKey "The fieldType of uniqueKey must not be analyzed...." (hence my comment baout "possible, but hard to get right ... you can use something like the KeywordTokenizer, but at that point you might as well use StrField except in some really esoteric special situations) -Hoss http://www.lucidworks.com/
