Hi KrishnaVamsi,

You may find this helpful. It is related to local params, but the symptoms are 
the same: 
https://stackoverflow.com/questions/58812890/local-param-not-working-in-solr-8-but-working-in-solr-5.
 Newer versions of Solr have introduced additional validation checks, and in 
this case, it looks like commas are recognized as part of the field name and 
not as a separator.

Kind regards,

Patryk

On 2024/09/13 07:00:27 "Mugi, Krishnavamsireddy" wrote:
> Hi Mikhail,
> 
> Request parameters --> 
> defType=edismax&indent=true&q.op=OR&q=*:*&qf=sourceRefId_t, 
> channelName_t&useParams=&wt=json
> 
> Error: 
> 
> "error":{
>     "metadata":[
>       "error-class","org.apache.solr.common.SolrException",
>       "root-error-class","org.apache.solr.common.SolrException"],
>     "msg":"org.apache.solr.search.SyntaxError: Query Field 'sourceRefId_t,' 
> is not a valid field name",
>     "code":400}}
> 
> Solr is allowing either , or space in between the fields in qf parameter in 
> 9.6.1, But it is working fine in 6.5.1. How can we rectify this error, Please 
> let us know.
> 
> Thanks&Regards
> KrishnaVamsi
> 
> 
> -----Original Message-----
> From: Mikhail Khludnev <mk...@apache.org> 
> Sent: 13 September 2024 02:16
> To: users@solr.apache.org
> Subject: Re: Query related to solr 9.6.1
> 
> 
> <External Email>
> 
> 
> Hello
> Please share the exact error and request parameters.
> 
> On Wed, Sep 11, 2024 at 5:11 PM Mugi, Krishnavamsireddy < 
> krishnavamsireddy.m...@paramount.com> wrote:
> 
> > Hi Team,
> >
> > We have migrated our solr instance from 6.5.1 to 9.6.1.
> >
> > In 6.5.1, we were sending multiple fields in qf parameter in edisMax 
> > with spaces in between, Something like below. It was working fine.
> >
> > qf=workflowId_t, originalTitle_t, sourceRefId_t
> >
> > Same thing we are trying to do in 9.6.1, we are getting solr exception 
> > that query field is not present. Can someone please help me on this?
> >
> > Thanks&Regards
> > KrishnaVamsi
> >
> >
> 
> --
> Sincerely yours
> Mikhail Khludnev
> 

Reply via email to