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

Mikhail Khludnev resolved SOLR-9620.
------------------------------------
       Resolution: Fixed
    Fix Version/s: 6.4

It's resolved only in {{6x}}, since {{master (7.0)}} doesn't support join by 
numeric. 

> {!join score=.. fromIndex=..} throws "undefined field" for numeric field if 
> from and to schemas are different 
> --------------------------------------------------------------------------------------------------------------
>
>                 Key: SOLR-9620
>                 URL: https://issues.apache.org/jira/browse/SOLR-9620
>             Project: Solr
>          Issue Type: Bug
>      Security Level: Public(Default Security Level. Issues are Public) 
>    Affects Versions: 6.3
>            Reporter: Mikhail Khludnev
>            Assignee: Mikhail Khludnev
>             Fix For: 6.4
>
>         Attachments: SOLR-9620.patch
>
>
> numeric "from" field is mistakenly looked in "to" schema. see 
> org.apache.solr.search.join.ScoreJoinQParserPlugin.....parse()
> {code}
>        private Query createQuery(final String fromField, final String 
> fromQueryStr,
>                                  String fromIndex, final String toField, 
> final ScoreMode scoreMode,
>                                  boolean byPassShortCircutCheck) throws 
> SyntaxError {
> +        FieldType.LegacyNumericType fromNumericType = 
> req.getSchema().getField(fromField).getType().getNumericType();
> +        FieldType.LegacyNumericType toNumericType = 
> req.getSchema().getField(toField).getType().getNumericType();
> {code}
> it's in branch_6x only. Users who are faced this are advised to just declare 
> "from" field in "to" schema. It should work. Take care.  
> one line fix and improvements for TestCrossCoreJoin.java are quite welcome. 
>  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to