Re: Manipulating client's query using a Query object

2020-08-17 Thread Erick Erickson
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

Re: Manipulating client's query using a Query object

2020-08-17 Thread Edward Turner
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

RE: Manipulating client's query using a Query object

2020-08-17 Thread Markus Jelsma
Dismax has some variable (i think it was qstr) that contains the original 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 > Subject: Re: Manipula

Re: Manipulating client's query using a Query object

2020-08-17 Thread Edward Turner
Hi Markus, That's really great info. Thank you. Supposing we've now modified the Query object, do you know how we would get the corresponding query String, which we could then forward to our Solrcloud via SolrClient? (Or should we be using this extended ExtendedDisMaxQParser class server side in

RE: Manipulating client's query using a Query object

2020-08-17 Thread Markus Jelsma
Hello Edward, Yes you can by extending ExtendedDismaxQParser [1] and override its parse() method. You get the main Query object through super.parse(). If you need even more fine grained control on how Query objects are created you can extend ExtendedSolrQueryParser's [2] (inner class) newFieldQ