You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@solr.apache.org by Andy Coulson <an...@epicor.com> on 2021/09/09 21:23:56 UTC
qf with multiple fields in _query_ with edismax
There is precious little documentation on the _query_ magic field, but from what I understand, it should take whatever parameters are supported by parser.
I am trying to provide multiple filed names to the qf parameter, but nothing I try works. Examples I have found googling indicate my syntax should be ok.
I am using the edismax parser and version 6.6
I try this, where the term "r" does exists in thing_name (but not in object_name), but get no results:
http://localhost:8983/solr/myCore/select?q=_query_:"{!edismax%20qf=object_name%20thing_name}r"&fl=*%2Cscore
example also suggest that having the fl parameter inside the braces should work, but it is ignored, as are other edismax params like mm.
Andy Coulson
Principal Software Engineer
Epicor Software Corporation
www.epicor.com<http://www.epicor.com>
Tel.: (512) 328-2300
Cell: (512) 517-2494
E-Mail: andy.coulson@epicor.com<ma...@epicor.com>
[cid:image003.jpg@01D7A597.14F479D0]
RE: qf with multiple fields in _query_ with edismax
Posted by Andy Coulson <an...@epicor.com>.
We're also looking at Solrj to insulate us from the protocol layer entirely.
-----Original Message-----
From: Andy Coulson <an...@epicor.com>
Sent: Friday, September 10, 2021 10:37 AM
To: users@solr.apache.org
Subject: RE: qf with multiple fields in _query_ with edismax
Ahh, so yes, now I see. That is probably a better approach as we actually implement this.
-----Original Message-----
From: Jan Høydahl <ja...@cominvent.com>
Sent: Friday, September 10, 2021 10:12 AM
To: users@solr.apache.org
Subject: Re: qf with multiple fields in _query_ with edismax
And if you fancy looking into the JSON Query DSL (https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsolr.apache.org%2Fguide%2F8_9%2Fjson-query-dsl.html&data=04%7C01%7Candy.coulson%40epicor.com%7Ce88ff92cb36442c81d7f08d97470d04c%7C4f4f4c56a772461a967e7890c3960b3a%7C1%7C0%7C637668850143444313%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=b%2FTwOfhUtoVmsABYIkJNVRM45gYVGkp34q%2BqrVY0iWw%3D&reserved=0) then it would look something like this
curl -X POST http://localhost:8983/solr/techproducts/query -d '
{
"query": {
"bool": {
"must": [
"name:iPod",
"cat:electronics",
{"edismax": {"qf": "cat name", "pf": "cat^10", "mm": "100%", "query": "mini"}}
]
}
}
}'
Unfortunately we don't have good Admin UI support for editing JSON DSL yet.
Jan
> 10. sep. 2021 kl. 16:33 skrev David Hastings <ha...@gmail.com>:
>
> Do you mind if I ask why not use a post to solr?
>
> On Fri, Sep 10, 2021 at 10:18 AM Andy Coulson
> <an...@epicor.com>
> wrote:
>
>> Thanks Erik,
>>
>> That did the trick! My real use case will have additional predicates
>> - I merely trimmed it down to reproduce and illustrate the problem. I
>> real query will probably be something like (without encoding):
>>
>> q= locale:en AND thingType:part AND _query_:"{!edismax
>> qf='object_name thing_name' pf=thing_name^10 v=$qq
>> mm=$minMatch}"&qq=clutch cable&minMatch=100%&fl=*,score
>>
>> -----Original Message-----
>> From: Erik Hatcher <er...@gmail.com>
>> Sent: Friday, September 10, 2021 8:40 AM
>> To: users@solr.apache.org
>> Subject: Re: qf with multiple fields in _query_ with edismax
>>
>> Andy,
>>
>> Use single quotes around the inner parameters, such as {!edismax
>> qf='object_name thing_name'}. Going even further, use the `v`
>> parameter to encapsulate the query string inside as well, as the parser eats everything
>> after the closing curly bracket otherwise. {!edismax qf='object_name
>> thing_name' v='r'}. Beyond that, if the query string is potentially
>> complex, and may itself contain a single quote, use param indirection....
>>
>> q={!edismax qf='object_name thing_name' v=$qq mm='100%'}&qq=r
>>
>> If you're only doing a single edismax, then using the _query_ here is
>> not necessary though.
>>
>> Erik
>>
>>
>>
>>> On Sep 9, 2021, at 5:23 PM, Andy Coulson <an...@epicor.com>
>> wrote:
>>>
>>> There is precious little documentation on the _query_ magic field,
>>> but
>> from what I understand, it should take whatever parameters are
>> supported by parser.
>>> I am trying to provide multiple filed names to the qf parameter, but
>> nothing I try works. Examples I have found googling indicate my
>> syntax should be ok.
>>>
>>> I am using the edismax parser and version 6.6
>>>
>>> I try this, where the term "r" does exists in thing_name (but not in
>> object_name), but get no results:
>>> http://localhost:8983/solr/myCore/select?q=_query_ <
>> http://localhost:8983/solr/myCore/select?q=_query_
>>> :"{!edismax%20qf=object_name%20thing_name}r"&fl=*%2Cscore
>>>
>>> example also suggest that having the fl parameter inside the braces
>> should work, but it is ignored, as are other edismax params like mm.
>>>
>>> Andy Coulson
>>> Principal Software Engineer
>>> Epicor Software Corporation
>>> www.epicor.com <http://www.epicor.com/>
>>> Tel.: (512) 328-2300
>>> Cell: (512) 517-2494
>>> E-Mail: andy.coulson@epicor.com <ma...@epicor.com>
>>
>>
RE: qf with multiple fields in _query_ with edismax
Posted by Andy Coulson <an...@epicor.com>.
Ahh, so yes, now I see. That is probably a better approach as we actually implement this.
-----Original Message-----
From: Jan Høydahl <ja...@cominvent.com>
Sent: Friday, September 10, 2021 10:12 AM
To: users@solr.apache.org
Subject: Re: qf with multiple fields in _query_ with edismax
And if you fancy looking into the JSON Query DSL (https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsolr.apache.org%2Fguide%2F8_9%2Fjson-query-dsl.html&data=04%7C01%7Candy.coulson%40epicor.com%7C7c415b72e40a43705df108d9746d69f2%7C4f4f4c56a772461a967e7890c3960b3a%7C1%7C0%7C637668835539221078%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=IZSMQApxuiGbfOFRogQ%2BN1z6nUmAc1fq1BJgxk2FWVA%3D&reserved=0) then it would look something like this
curl -X POST http://localhost:8983/solr/techproducts/query -d '
{
"query": {
"bool": {
"must": [
"name:iPod",
"cat:electronics",
{"edismax": {"qf": "cat name", "pf": "cat^10", "mm": "100%", "query": "mini"}}
]
}
}
}'
Unfortunately we don't have good Admin UI support for editing JSON DSL yet.
Jan
> 10. sep. 2021 kl. 16:33 skrev David Hastings <ha...@gmail.com>:
>
> Do you mind if I ask why not use a post to solr?
>
> On Fri, Sep 10, 2021 at 10:18 AM Andy Coulson
> <an...@epicor.com>
> wrote:
>
>> Thanks Erik,
>>
>> That did the trick! My real use case will have additional predicates
>> - I merely trimmed it down to reproduce and illustrate the problem. I
>> real query will probably be something like (without encoding):
>>
>> q= locale:en AND thingType:part AND _query_:"{!edismax
>> qf='object_name thing_name' pf=thing_name^10 v=$qq
>> mm=$minMatch}"&qq=clutch cable&minMatch=100%&fl=*,score
>>
>> -----Original Message-----
>> From: Erik Hatcher <er...@gmail.com>
>> Sent: Friday, September 10, 2021 8:40 AM
>> To: users@solr.apache.org
>> Subject: Re: qf with multiple fields in _query_ with edismax
>>
>> Andy,
>>
>> Use single quotes around the inner parameters, such as {!edismax
>> qf='object_name thing_name'}. Going even further, use the `v`
>> parameter to encapsulate the query string inside as well, as the parser eats everything
>> after the closing curly bracket otherwise. {!edismax qf='object_name
>> thing_name' v='r'}. Beyond that, if the query string is potentially
>> complex, and may itself contain a single quote, use param indirection....
>>
>> q={!edismax qf='object_name thing_name' v=$qq mm='100%'}&qq=r
>>
>> If you're only doing a single edismax, then using the _query_ here is
>> not necessary though.
>>
>> Erik
>>
>>
>>
>>> On Sep 9, 2021, at 5:23 PM, Andy Coulson <an...@epicor.com>
>> wrote:
>>>
>>> There is precious little documentation on the _query_ magic field,
>>> but
>> from what I understand, it should take whatever parameters are
>> supported by parser.
>>> I am trying to provide multiple filed names to the qf parameter, but
>> nothing I try works. Examples I have found googling indicate my
>> syntax should be ok.
>>>
>>> I am using the edismax parser and version 6.6
>>>
>>> I try this, where the term "r" does exists in thing_name (but not in
>> object_name), but get no results:
>>> http://localhost:8983/solr/myCore/select?q=_query_ <
>> http://localhost:8983/solr/myCore/select?q=_query_
>>> :"{!edismax%20qf=object_name%20thing_name}r"&fl=*%2Cscore
>>>
>>> example also suggest that having the fl parameter inside the braces
>> should work, but it is ignored, as are other edismax params like mm.
>>>
>>> Andy Coulson
>>> Principal Software Engineer
>>> Epicor Software Corporation
>>> www.epicor.com <http://www.epicor.com/>
>>> Tel.: (512) 328-2300
>>> Cell: (512) 517-2494
>>> E-Mail: andy.coulson@epicor.com <ma...@epicor.com>
>>
>>
Re: qf with multiple fields in _query_ with edismax
Posted by Jan Høydahl <ja...@cominvent.com>.
And if you fancy looking into the JSON Query DSL (https://solr.apache.org/guide/8_9/json-query-dsl.html) then it would look something like this
curl -X POST http://localhost:8983/solr/techproducts/query -d '
{
"query": {
"bool": {
"must": [
"name:iPod",
"cat:electronics",
{"edismax": {"qf": "cat name", "pf": "cat^10", "mm": "100%", "query": "mini"}}
]
}
}
}'
Unfortunately we don't have good Admin UI support for editing JSON DSL yet.
Jan
> 10. sep. 2021 kl. 16:33 skrev David Hastings <ha...@gmail.com>:
>
> Do you mind if I ask why not use a post to solr?
>
> On Fri, Sep 10, 2021 at 10:18 AM Andy Coulson <an...@epicor.com>
> wrote:
>
>> Thanks Erik,
>>
>> That did the trick! My real use case will have additional predicates - I
>> merely trimmed it down to reproduce and illustrate the problem. I real
>> query will probably be something like (without encoding):
>>
>> q= locale:en AND thingType:part AND _query_:"{!edismax qf='object_name
>> thing_name' pf=thing_name^10 v=$qq mm=$minMatch}"&qq=clutch
>> cable&minMatch=100%&fl=*,score
>>
>> -----Original Message-----
>> From: Erik Hatcher <er...@gmail.com>
>> Sent: Friday, September 10, 2021 8:40 AM
>> To: users@solr.apache.org
>> Subject: Re: qf with multiple fields in _query_ with edismax
>>
>> Andy,
>>
>> Use single quotes around the inner parameters, such as {!edismax
>> qf='object_name thing_name'}. Going even further, use the `v` parameter to
>> encapsulate the query string inside as well, as the parser eats everything
>> after the closing curly bracket otherwise. {!edismax qf='object_name
>> thing_name' v='r'}. Beyond that, if the query string is potentially
>> complex, and may itself contain a single quote, use param indirection....
>>
>> q={!edismax qf='object_name thing_name' v=$qq mm='100%'}&qq=r
>>
>> If you're only doing a single edismax, then using the _query_ here is not
>> necessary though.
>>
>> Erik
>>
>>
>>
>>> On Sep 9, 2021, at 5:23 PM, Andy Coulson <an...@epicor.com>
>> wrote:
>>>
>>> There is precious little documentation on the _query_ magic field, but
>> from what I understand, it should take whatever parameters are supported by
>> parser.
>>> I am trying to provide multiple filed names to the qf parameter, but
>> nothing I try works. Examples I have found googling indicate my syntax
>> should be ok.
>>>
>>> I am using the edismax parser and version 6.6
>>>
>>> I try this, where the term "r" does exists in thing_name (but not in
>> object_name), but get no results:
>>> http://localhost:8983/solr/myCore/select?q=_query_ <
>> http://localhost:8983/solr/myCore/select?q=_query_
>>> :"{!edismax%20qf=object_name%20thing_name}r"&fl=*%2Cscore
>>>
>>> example also suggest that having the fl parameter inside the braces
>> should work, but it is ignored, as are other edismax params like mm.
>>>
>>> Andy Coulson
>>> Principal Software Engineer
>>> Epicor Software Corporation
>>> www.epicor.com <http://www.epicor.com/>
>>> Tel.: (512) 328-2300
>>> Cell: (512) 517-2494
>>> E-Mail: andy.coulson@epicor.com <ma...@epicor.com>
>>
>>
Re: qf with multiple fields in _query_ with edismax
Posted by Dave <ha...@gmail.com>.
Ah, I just looked at my code and I just replace single quotes with a space since it’s the same thing. Thanks for the clarification my bad for bad info. I still prefer a post over a get however
> On Sep 11, 2021, at 12:55 PM, Erik Hatcher <er...@gmail.com> wrote:
>
> That's not true in this case Dave. The single quotes are needed to
> encapsulate an inner parameter value that has spaces. It's not a get vs
> post thing for this.
>
> Erik
>
>> On Fri, Sep 10, 2021, 11:45 Dave <ha...@gmail.com> wrote:
>>
>> With a post you don’t have to worry about single/double quotes or any
>> other characters like an @ or & in your query, they all go in as is from
>> the user input, maybe not using curl but every language has a post
>> operation to utilize. Kind of like placeholders for a sql query, they can
>> contain anything and you don’t have to clean the user input (php bad Perl
>> good)
>>
>>> On Sep 10, 2021, at 11:35 AM, Andy Coulson <an...@epicor.com>
>> wrote:
>>>
>>> I'm not sure what you mean? If you mean why use a get vs a post, I
>> guess just because we started with copying the url generated by the UI
>> query console and just kept tweaking that. I supposed we could also just
>> use postman to experiment using posts if that is supported.
>>>
>>> -----Original Message-----
>>> From: David Hastings <ha...@gmail.com>
>>> Sent: Friday, September 10, 2021 9:34 AM
>>> To: users@solr.apache.org
>>> Subject: Re: qf with multiple fields in _query_ with edismax
>>>
>>> Do you mind if I ask why not use a post to solr?
>>>
>>>> On Fri, Sep 10, 2021 at 10:18 AM Andy Coulson <an...@epicor.com>
>>>> wrote:
>>>>
>>>> Thanks Erik,
>>>>
>>>> That did the trick! My real use case will have additional predicates -
>>>> I merely trimmed it down to reproduce and illustrate the problem. I
>>>> real query will probably be something like (without encoding):
>>>>
>>>> q= locale:en AND thingType:part AND _query_:"{!edismax qf='object_name
>>>> thing_name' pf=thing_name^10 v=$qq mm=$minMatch}"&qq=clutch
>>>> cable&minMatch=100%&fl=*,score
>>>>
>>>> -----Original Message-----
>>>> From: Erik Hatcher <er...@gmail.com>
>>>> Sent: Friday, September 10, 2021 8:40 AM
>>>> To: users@solr.apache.org
>>>> Subject: Re: qf with multiple fields in _query_ with edismax
>>>>
>>>> Andy,
>>>>
>>>> Use single quotes around the inner parameters, such as {!edismax
>>>> qf='object_name thing_name'}. Going even further, use the `v`
>>>> parameter to encapsulate the query string inside as well, as the parser
>> eats everything
>>>> after the closing curly bracket otherwise. {!edismax qf='object_name
>>>> thing_name' v='r'}. Beyond that, if the query string is potentially
>>>> complex, and may itself contain a single quote, use param
>> indirection....
>>>>
>>>> q={!edismax qf='object_name thing_name' v=$qq mm='100%'}&qq=r
>>>>
>>>> If you're only doing a single edismax, then using the _query_ here is
>>>> not necessary though.
>>>>
>>>> Erik
>>>>
>>>>
>>>>
>>>>> On Sep 9, 2021, at 5:23 PM, Andy Coulson <an...@epicor.com>
>>>> wrote:
>>>>>
>>>>> There is precious little documentation on the _query_ magic field,
>>>>> but
>>>> from what I understand, it should take whatever parameters are
>>>> supported by parser.
>>>>> I am trying to provide multiple filed names to the qf parameter, but
>>>> nothing I try works. Examples I have found googling indicate my syntax
>>>> should be ok.
>>>>>
>>>>> I am using the edismax parser and version 6.6
>>>>>
>>>>> I try this, where the term "r" does exists in thing_name (but not in
>>>> object_name), but get no results:
>>>>> http://localhost:8983/solr/myCore/select?q=_query_ <
>>>> http://localhost:8983/solr/myCore/select?q=_query_
>>>>> :"{!edismax%20qf=object_name%20thing_name}r"&fl=*%2Cscore
>>>>>
>>>>> example also suggest that having the fl parameter inside the braces
>>>> should work, but it is ignored, as are other edismax params like mm.
>>>>>
>>>>> Andy Coulson
>>>>> Principal Software Engineer
>>>>> Epicor Software Corporation
>>>>> www.epicor.com <http://www.epicor.com/>
>>>>> Tel.: (512) 328-2300
>>>>> Cell: (512) 517-2494
>>>>> E-Mail: andy.coulson@epicor.com <ma...@epicor.com>
>>>>
>>>>
>>
Re: qf with multiple fields in _query_ with edismax
Posted by Erik Hatcher <er...@gmail.com>.
That's not true in this case Dave. The single quotes are needed to
encapsulate an inner parameter value that has spaces. It's not a get vs
post thing for this.
Erik
On Fri, Sep 10, 2021, 11:45 Dave <ha...@gmail.com> wrote:
> With a post you don’t have to worry about single/double quotes or any
> other characters like an @ or & in your query, they all go in as is from
> the user input, maybe not using curl but every language has a post
> operation to utilize. Kind of like placeholders for a sql query, they can
> contain anything and you don’t have to clean the user input (php bad Perl
> good)
>
> > On Sep 10, 2021, at 11:35 AM, Andy Coulson <an...@epicor.com>
> wrote:
> >
> > I'm not sure what you mean? If you mean why use a get vs a post, I
> guess just because we started with copying the url generated by the UI
> query console and just kept tweaking that. I supposed we could also just
> use postman to experiment using posts if that is supported.
> >
> > -----Original Message-----
> > From: David Hastings <ha...@gmail.com>
> > Sent: Friday, September 10, 2021 9:34 AM
> > To: users@solr.apache.org
> > Subject: Re: qf with multiple fields in _query_ with edismax
> >
> > Do you mind if I ask why not use a post to solr?
> >
> >> On Fri, Sep 10, 2021 at 10:18 AM Andy Coulson <an...@epicor.com>
> >> wrote:
> >>
> >> Thanks Erik,
> >>
> >> That did the trick! My real use case will have additional predicates -
> >> I merely trimmed it down to reproduce and illustrate the problem. I
> >> real query will probably be something like (without encoding):
> >>
> >> q= locale:en AND thingType:part AND _query_:"{!edismax qf='object_name
> >> thing_name' pf=thing_name^10 v=$qq mm=$minMatch}"&qq=clutch
> >> cable&minMatch=100%&fl=*,score
> >>
> >> -----Original Message-----
> >> From: Erik Hatcher <er...@gmail.com>
> >> Sent: Friday, September 10, 2021 8:40 AM
> >> To: users@solr.apache.org
> >> Subject: Re: qf with multiple fields in _query_ with edismax
> >>
> >> Andy,
> >>
> >> Use single quotes around the inner parameters, such as {!edismax
> >> qf='object_name thing_name'}. Going even further, use the `v`
> >> parameter to encapsulate the query string inside as well, as the parser
> eats everything
> >> after the closing curly bracket otherwise. {!edismax qf='object_name
> >> thing_name' v='r'}. Beyond that, if the query string is potentially
> >> complex, and may itself contain a single quote, use param
> indirection....
> >>
> >> q={!edismax qf='object_name thing_name' v=$qq mm='100%'}&qq=r
> >>
> >> If you're only doing a single edismax, then using the _query_ here is
> >> not necessary though.
> >>
> >> Erik
> >>
> >>
> >>
> >>> On Sep 9, 2021, at 5:23 PM, Andy Coulson <an...@epicor.com>
> >> wrote:
> >>>
> >>> There is precious little documentation on the _query_ magic field,
> >>> but
> >> from what I understand, it should take whatever parameters are
> >> supported by parser.
> >>> I am trying to provide multiple filed names to the qf parameter, but
> >> nothing I try works. Examples I have found googling indicate my syntax
> >> should be ok.
> >>>
> >>> I am using the edismax parser and version 6.6
> >>>
> >>> I try this, where the term "r" does exists in thing_name (but not in
> >> object_name), but get no results:
> >>> http://localhost:8983/solr/myCore/select?q=_query_ <
> >> http://localhost:8983/solr/myCore/select?q=_query_
> >>> :"{!edismax%20qf=object_name%20thing_name}r"&fl=*%2Cscore
> >>>
> >>> example also suggest that having the fl parameter inside the braces
> >> should work, but it is ignored, as are other edismax params like mm.
> >>>
> >>> Andy Coulson
> >>> Principal Software Engineer
> >>> Epicor Software Corporation
> >>> www.epicor.com <http://www.epicor.com/>
> >>> Tel.: (512) 328-2300
> >>> Cell: (512) 517-2494
> >>> E-Mail: andy.coulson@epicor.com <ma...@epicor.com>
> >>
> >>
>
Re: qf with multiple fields in _query_ with edismax
Posted by Dave <ha...@gmail.com>.
With a post you don’t have to worry about single/double quotes or any other characters like an @ or & in your query, they all go in as is from the user input, maybe not using curl but every language has a post operation to utilize. Kind of like placeholders for a sql query, they can contain anything and you don’t have to clean the user input (php bad Perl good)
> On Sep 10, 2021, at 11:35 AM, Andy Coulson <an...@epicor.com> wrote:
>
> I'm not sure what you mean? If you mean why use a get vs a post, I guess just because we started with copying the url generated by the UI query console and just kept tweaking that. I supposed we could also just use postman to experiment using posts if that is supported.
>
> -----Original Message-----
> From: David Hastings <ha...@gmail.com>
> Sent: Friday, September 10, 2021 9:34 AM
> To: users@solr.apache.org
> Subject: Re: qf with multiple fields in _query_ with edismax
>
> Do you mind if I ask why not use a post to solr?
>
>> On Fri, Sep 10, 2021 at 10:18 AM Andy Coulson <an...@epicor.com>
>> wrote:
>>
>> Thanks Erik,
>>
>> That did the trick! My real use case will have additional predicates -
>> I merely trimmed it down to reproduce and illustrate the problem. I
>> real query will probably be something like (without encoding):
>>
>> q= locale:en AND thingType:part AND _query_:"{!edismax qf='object_name
>> thing_name' pf=thing_name^10 v=$qq mm=$minMatch}"&qq=clutch
>> cable&minMatch=100%&fl=*,score
>>
>> -----Original Message-----
>> From: Erik Hatcher <er...@gmail.com>
>> Sent: Friday, September 10, 2021 8:40 AM
>> To: users@solr.apache.org
>> Subject: Re: qf with multiple fields in _query_ with edismax
>>
>> Andy,
>>
>> Use single quotes around the inner parameters, such as {!edismax
>> qf='object_name thing_name'}. Going even further, use the `v`
>> parameter to encapsulate the query string inside as well, as the parser eats everything
>> after the closing curly bracket otherwise. {!edismax qf='object_name
>> thing_name' v='r'}. Beyond that, if the query string is potentially
>> complex, and may itself contain a single quote, use param indirection....
>>
>> q={!edismax qf='object_name thing_name' v=$qq mm='100%'}&qq=r
>>
>> If you're only doing a single edismax, then using the _query_ here is
>> not necessary though.
>>
>> Erik
>>
>>
>>
>>> On Sep 9, 2021, at 5:23 PM, Andy Coulson <an...@epicor.com>
>> wrote:
>>>
>>> There is precious little documentation on the _query_ magic field,
>>> but
>> from what I understand, it should take whatever parameters are
>> supported by parser.
>>> I am trying to provide multiple filed names to the qf parameter, but
>> nothing I try works. Examples I have found googling indicate my syntax
>> should be ok.
>>>
>>> I am using the edismax parser and version 6.6
>>>
>>> I try this, where the term "r" does exists in thing_name (but not in
>> object_name), but get no results:
>>> http://localhost:8983/solr/myCore/select?q=_query_ <
>> http://localhost:8983/solr/myCore/select?q=_query_
>>> :"{!edismax%20qf=object_name%20thing_name}r"&fl=*%2Cscore
>>>
>>> example also suggest that having the fl parameter inside the braces
>> should work, but it is ignored, as are other edismax params like mm.
>>>
>>> Andy Coulson
>>> Principal Software Engineer
>>> Epicor Software Corporation
>>> www.epicor.com <http://www.epicor.com/>
>>> Tel.: (512) 328-2300
>>> Cell: (512) 517-2494
>>> E-Mail: andy.coulson@epicor.com <ma...@epicor.com>
>>
>>
RE: qf with multiple fields in _query_ with edismax
Posted by Andy Coulson <an...@epicor.com>.
I'm not sure what you mean? If you mean why use a get vs a post, I guess just because we started with copying the url generated by the UI query console and just kept tweaking that. I supposed we could also just use postman to experiment using posts if that is supported.
-----Original Message-----
From: David Hastings <ha...@gmail.com>
Sent: Friday, September 10, 2021 9:34 AM
To: users@solr.apache.org
Subject: Re: qf with multiple fields in _query_ with edismax
Do you mind if I ask why not use a post to solr?
On Fri, Sep 10, 2021 at 10:18 AM Andy Coulson <an...@epicor.com>
wrote:
> Thanks Erik,
>
> That did the trick! My real use case will have additional predicates -
> I merely trimmed it down to reproduce and illustrate the problem. I
> real query will probably be something like (without encoding):
>
> q= locale:en AND thingType:part AND _query_:"{!edismax qf='object_name
> thing_name' pf=thing_name^10 v=$qq mm=$minMatch}"&qq=clutch
> cable&minMatch=100%&fl=*,score
>
> -----Original Message-----
> From: Erik Hatcher <er...@gmail.com>
> Sent: Friday, September 10, 2021 8:40 AM
> To: users@solr.apache.org
> Subject: Re: qf with multiple fields in _query_ with edismax
>
> Andy,
>
> Use single quotes around the inner parameters, such as {!edismax
> qf='object_name thing_name'}. Going even further, use the `v`
> parameter to encapsulate the query string inside as well, as the parser eats everything
> after the closing curly bracket otherwise. {!edismax qf='object_name
> thing_name' v='r'}. Beyond that, if the query string is potentially
> complex, and may itself contain a single quote, use param indirection....
>
> q={!edismax qf='object_name thing_name' v=$qq mm='100%'}&qq=r
>
> If you're only doing a single edismax, then using the _query_ here is
> not necessary though.
>
> Erik
>
>
>
> > On Sep 9, 2021, at 5:23 PM, Andy Coulson <an...@epicor.com>
> wrote:
> >
> > There is precious little documentation on the _query_ magic field,
> > but
> from what I understand, it should take whatever parameters are
> supported by parser.
> > I am trying to provide multiple filed names to the qf parameter, but
> nothing I try works. Examples I have found googling indicate my syntax
> should be ok.
> >
> > I am using the edismax parser and version 6.6
> >
> > I try this, where the term "r" does exists in thing_name (but not in
> object_name), but get no results:
> > http://localhost:8983/solr/myCore/select?q=_query_ <
> http://localhost:8983/solr/myCore/select?q=_query_
> >:"{!edismax%20qf=object_name%20thing_name}r"&fl=*%2Cscore
> >
> > example also suggest that having the fl parameter inside the braces
> should work, but it is ignored, as are other edismax params like mm.
> >
> > Andy Coulson
> > Principal Software Engineer
> > Epicor Software Corporation
> > www.epicor.com <http://www.epicor.com/>
> > Tel.: (512) 328-2300
> > Cell: (512) 517-2494
> > E-Mail: andy.coulson@epicor.com <ma...@epicor.com>
>
>
Re: qf with multiple fields in _query_ with edismax
Posted by David Hastings <ha...@gmail.com>.
Do you mind if I ask why not use a post to solr?
On Fri, Sep 10, 2021 at 10:18 AM Andy Coulson <an...@epicor.com>
wrote:
> Thanks Erik,
>
> That did the trick! My real use case will have additional predicates - I
> merely trimmed it down to reproduce and illustrate the problem. I real
> query will probably be something like (without encoding):
>
> q= locale:en AND thingType:part AND _query_:"{!edismax qf='object_name
> thing_name' pf=thing_name^10 v=$qq mm=$minMatch}"&qq=clutch
> cable&minMatch=100%&fl=*,score
>
> -----Original Message-----
> From: Erik Hatcher <er...@gmail.com>
> Sent: Friday, September 10, 2021 8:40 AM
> To: users@solr.apache.org
> Subject: Re: qf with multiple fields in _query_ with edismax
>
> Andy,
>
> Use single quotes around the inner parameters, such as {!edismax
> qf='object_name thing_name'}. Going even further, use the `v` parameter to
> encapsulate the query string inside as well, as the parser eats everything
> after the closing curly bracket otherwise. {!edismax qf='object_name
> thing_name' v='r'}. Beyond that, if the query string is potentially
> complex, and may itself contain a single quote, use param indirection....
>
> q={!edismax qf='object_name thing_name' v=$qq mm='100%'}&qq=r
>
> If you're only doing a single edismax, then using the _query_ here is not
> necessary though.
>
> Erik
>
>
>
> > On Sep 9, 2021, at 5:23 PM, Andy Coulson <an...@epicor.com>
> wrote:
> >
> > There is precious little documentation on the _query_ magic field, but
> from what I understand, it should take whatever parameters are supported by
> parser.
> > I am trying to provide multiple filed names to the qf parameter, but
> nothing I try works. Examples I have found googling indicate my syntax
> should be ok.
> >
> > I am using the edismax parser and version 6.6
> >
> > I try this, where the term "r" does exists in thing_name (but not in
> object_name), but get no results:
> > http://localhost:8983/solr/myCore/select?q=_query_ <
> http://localhost:8983/solr/myCore/select?q=_query_
> >:"{!edismax%20qf=object_name%20thing_name}r"&fl=*%2Cscore
> >
> > example also suggest that having the fl parameter inside the braces
> should work, but it is ignored, as are other edismax params like mm.
> >
> > Andy Coulson
> > Principal Software Engineer
> > Epicor Software Corporation
> > www.epicor.com <http://www.epicor.com/>
> > Tel.: (512) 328-2300
> > Cell: (512) 517-2494
> > E-Mail: andy.coulson@epicor.com <ma...@epicor.com>
>
>
RE: qf with multiple fields in _query_ with edismax
Posted by Andy Coulson <an...@epicor.com>.
Thanks Erik,
That did the trick! My real use case will have additional predicates - I merely trimmed it down to reproduce and illustrate the problem. I real query will probably be something like (without encoding):
q= locale:en AND thingType:part AND _query_:"{!edismax qf='object_name thing_name' pf=thing_name^10 v=$qq mm=$minMatch}"&qq=clutch cable&minMatch=100%&fl=*,score
-----Original Message-----
From: Erik Hatcher <er...@gmail.com>
Sent: Friday, September 10, 2021 8:40 AM
To: users@solr.apache.org
Subject: Re: qf with multiple fields in _query_ with edismax
Andy,
Use single quotes around the inner parameters, such as {!edismax qf='object_name thing_name'}. Going even further, use the `v` parameter to encapsulate the query string inside as well, as the parser eats everything after the closing curly bracket otherwise. {!edismax qf='object_name thing_name' v='r'}. Beyond that, if the query string is potentially complex, and may itself contain a single quote, use param indirection....
q={!edismax qf='object_name thing_name' v=$qq mm='100%'}&qq=r
If you're only doing a single edismax, then using the _query_ here is not necessary though.
Erik
> On Sep 9, 2021, at 5:23 PM, Andy Coulson <an...@epicor.com> wrote:
>
> There is precious little documentation on the _query_ magic field, but from what I understand, it should take whatever parameters are supported by parser.
> I am trying to provide multiple filed names to the qf parameter, but nothing I try works. Examples I have found googling indicate my syntax should be ok.
>
> I am using the edismax parser and version 6.6
>
> I try this, where the term "r" does exists in thing_name (but not in object_name), but get no results:
> http://localhost:8983/solr/myCore/select?q=_query_ <http://localhost:8983/solr/myCore/select?q=_query_>:"{!edismax%20qf=object_name%20thing_name}r"&fl=*%2Cscore
>
> example also suggest that having the fl parameter inside the braces should work, but it is ignored, as are other edismax params like mm.
>
> Andy Coulson
> Principal Software Engineer
> Epicor Software Corporation
> www.epicor.com <http://www.epicor.com/>
> Tel.: (512) 328-2300
> Cell: (512) 517-2494
> E-Mail: andy.coulson@epicor.com <ma...@epicor.com>
Re: qf with multiple fields in _query_ with edismax
Posted by Erik Hatcher <er...@gmail.com>.
Andy,
Use single quotes around the inner parameters, such as {!edismax qf='object_name thing_name'}. Going even further, use the `v` parameter to encapsulate the query string inside as well, as the parser eats everything after the closing curly bracket otherwise. {!edismax qf='object_name thing_name' v='r'}. Beyond that, if the query string is potentially complex, and may itself contain a single quote, use param indirection....
q={!edismax qf='object_name thing_name' v=$qq mm='100%'}&qq=r
If you're only doing a single edismax, then using the _query_ here is not necessary though.
Erik
> On Sep 9, 2021, at 5:23 PM, Andy Coulson <an...@epicor.com> wrote:
>
> There is precious little documentation on the _query_ magic field, but from what I understand, it should take whatever parameters are supported by parser.
> I am trying to provide multiple filed names to the qf parameter, but nothing I try works. Examples I have found googling indicate my syntax should be ok.
>
> I am using the edismax parser and version 6.6
>
> I try this, where the term “r” does exists in thing_name (but not in object_name), but get no results:
> http://localhost:8983/solr/myCore/select?q=_query_ <http://localhost:8983/solr/myCore/select?q=_query_>:"{!edismax%20qf=object_name%20thing_name}r"&fl=*%2Cscore
>
> example also suggest that having the fl parameter inside the braces should work, but it is ignored, as are other edismax params like mm.
>
> Andy Coulson
> Principal Software Engineer
> Epicor Software Corporation
> www.epicor.com <http://www.epicor.com/>
> Tel.: (512) 328-2300
> Cell: (512) 517-2494
> E-Mail: andy.coulson@epicor.com <ma...@epicor.com>