Weird. Did you try echoParams=all just to see what other defaults are
picked up.
It feels like it picks up default parser and maybe default "df" value that
points to not existing text field.
Maybe enable debug too to see what it expands to.
Regards,
Alex
On Sun, Nov 10, 2019, 9:26 PM Kaminski, Adi, <adi.kamin...@verint.com>
wrote:
> Hi,
> We are trying to mix the query clause and use different parsers with some
> syntax we've seen in the community.
> The idea to re-use all capabilities of the default query parser, and also
> xmlparser capabilities of position filter
> (which we asked about it previously and got some guidance from Solr
> community experts to use lucene SpanFirst for our use-case).
>
> We've tried to use a query consisting of two query parsers:
> q=_query_:"{!edismax qf=text_en}hello" _query_:"{!xmlparser}<SpanFirst
> fieldName="text_en" end="5"
> boost="1.2"><SpanTerm>world</SpanTerm></SpanFirst>"
>
> The response was HTTP 400 with message "undefined field text".
>
> Any idea what's wrong in the syntax, or maybe some direction to more
> official syntax of mixing parsers to query in different ways ?
>
> Thanks a lot in advance,
> Adi
>
>
>
> This electronic message may contain proprietary and confidential
> information of Verint Systems Inc., its affiliates and/or subsidiaries. The
> information is intended to be for the use of the individual(s) or
> entity(ies) named above. If you are not the intended recipient (or
> authorized to receive this e-mail for the intended recipient), you may not
> use, copy, disclose or distribute to anyone this message or any information
> contained in this message. If you have received this electronic message in
> error, please notify us by replying to this e-mail.
>
