[ 
https://issues.apache.org/jira/browse/SOLR-10830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hoss Man resolved SOLR-10830.
-----------------------------
       Resolution: Fixed
         Assignee: Hoss Man
    Fix Version/s: master (7.0)

NOTE: even though this is a "bug fix" i've made the choice to only commit it to 
master and not backport...

* if folks are using child docs with 6.x and their schema has a mismatch they 
have probably already noticed 
* if folks are *not* using child docs with 6.x, they may still have a schema 
missmatch they don't care about (ie: at some point htye changed the "id" 
definition from the sample configs but didn't change {{\_root\_}}) so i don't 
wnat to suddenly break things for them in a bug fix release.

I am -0 on anyone else making the choose to backport ... but I don't plan on 
doing it.

> 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
>            Assignee: Hoss Man
>             Fix For: master (7.0)
>
>         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]

Reply via email to