[SOLR-10829] IndexSchema should enforce that uniqueKey field must not be points based

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 6.7, 7.0
• Labels: numeric-tries-to-points
• Assignee: Chris M. Hostetter
• Reporter: Chris M. Hostetter
• Created: 06/Jun/17 22:19
• Updated: 08/Jun/19 15:19
• Resolved: 09/Jun/17 22:14

Description

if a uniqueKey field is defined, then the IndexSchema should fail fast & hard on startup if the field type of the specific uniqueKey uses "points" (ie: FieldType.isPointField())

The reason for this is because deleting by id, and overwriting existing documents are predicated on being able to use IndexWriter.deleteDocuments(Term...) and IndexWriter.updateDocument(Term, Iterable<..docs..>) respectively – but Points based fields have no "Term" that can be based to these methods.

IndexSchema.readSchema should fail fast in this case with a clear error (just like it does if the uniqueKey field is multivalued)

Issue Links

• is related to: SOLR-10834 test configs should be changed to stop using numeric based uniqueKey field
• relates to: SOLR-10830 Solr needs to enforce that _root_ field has the same fieldType as the uniqueKey field
• relates to: SOLR-10807 Randomize PointFields in all tests unless explicit reason not to