[SOLR-10830] Solr needs to enforce that _root_ field has the same fieldType as the uniqueKey field

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 7.0
• Assignee: Chris M. Hostetter
• Reporter: Chris M. Hostetter
• Created: 06/Jun/17 22:26
• Updated: 02/Oct/19 17:30
• Resolved: 13/Jun/17 17:23

Description

it's pretty important for correct childDocument behavior that the _root_ field have the same <fieldType/> as the uniqueKey field – but nothing seems to enforce that.

(I realized this while working on SOLR-10807 where i was forcing all fields to be Points based except for the uniqueKey field and got some weird errors in PeerSync that only related to replacing child documents – because the schema.xml has a TrieIntField based "id" field, but _root_ was using IntPointField – but the same problem could affect any schema if folks change the id from string to long, or int to string, and don't make the corrisponding change to the definition of _root_)

Issue Links

• is related to: SOLR-10829 IndexSchema should enforce that uniqueKey field must not be points based
• is related to: SOLR-10833 Numeric FooPointField classes inconsistent with TrieFooFields on malformed input: throw NumberFormatException