[
https://issues.apache.org/jira/browse/SOLR-10830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16048125#comment-16048125
]
ASF subversion and git services commented on SOLR-10830:
--------------------------------------------------------
Commit 6396cb759f8c799f381b0730636fa412761030ce in lucene-solr's branch
refs/heads/master from Chris Hostetter
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=6396cb7 ]
SOLR-10830: Solr now correctly enforces that the '_root_' field has the same
fieldType as the uniqueKey field
> 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, 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.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
