al input string. In there you have access to that too.
>>
>> Regards,
>> Markus
>>
>>
>> -Original message-
>>> From:Edward Turner
>>> Sent: Monday 17th August 2020 21:25
>>> To: solr-user@lucene.apache.org
>>> Su
g. In there you have access to that too.
>
> Regards,
> Markus
>
>
> -Original message-
> > From:Edward Turner
> > Sent: Monday 17th August 2020 21:25
> > To: solr-user@lucene.apache.org
> > Subject: Re: Manipulating client's query using a Quer
ene.apache.org/solr/8_6_0/solr-core/org/apache/solr/search/ExtendedDismaxQParser.ExtendedSolrQueryParser.html
> >
> > -Original message-
> > > From:Edward Turner
> > > Sent: Monday 17th August 2020 15:53
> > > To: solr-user@lucene.apache.org
> > >
ache/solr/search/ExtendedDismaxQParser.html
> [2]
> https://lucene.apache.org/solr/8_6_0/solr-core/org/apache/solr/search/ExtendedDismaxQParser.ExtendedSolrQueryParser.html
>
> -Original message-
> > From:Edward Turner
> > Sent: Monday 17th August 2020 15:53
> > To: so
ssage-
> From:Edward Turner
> Sent: Monday 17th August 2020 15:53
> To: solr-user@lucene.apache.org
> Subject: Manipulating client's query using a Query object
>
> Hi all,
>
> Thanks for all your help recently. We're now using the edismax query parser
> and are happy wi
Hi all,
Thanks for all your help recently. We're now using the edismax query parser
and are happy with its behaviour. We have another question which maybe
someone can help with.
We have one use case where we optimise our query before sending it to Solr,
and we do this by manipulating the client's
