[
https://issues.apache.org/jira/browse/SOLR-10830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man updated SOLR-10830:
----------------------------
Attachment: SOLR-10830.patch
straight forward patch with tests
> Solr needs to enforce that _root_ field has the same fieldType as the
> uniqueKey field
> -------------------------------------------------------------------------------------
>
> Key: SOLR-10830
> URL: https://issues.apache.org/jira/browse/SOLR-10830
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Hoss Man
> Attachments: SOLR-10830.patch
>
>
> 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_}})
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
