Hi, Thanks for looping back in. We use Master-Slave! I resolved this one with handleSelect=true , removing /select handler from config and created another requesthandler (with a different name - other than select) and marking that as default="true". Now all the requests with qt param are handled by this request handler while the one specifying qt goes to the designated handlers. The application I am working on has different request handlers - like for the different types of suggestions, spellchecking, default search request etc and the code leverage solrj with qt param to dispatch requests to different handlers.
I hope that was the right way to go about it. On Tue, Mar 10, 2020 at 8:26 AM Mikhail Khludnev <m...@apache.org> wrote: > Hello, Atita. > > My question here is that on Solr 6.2.6 to enable using 'qt' param I need to > > do handleSelect=false > > Can you elaborate on that? What exactly happens? Also, please clarify > whether you use SolrCloud or standalone? > > > On Mon, Mar 2, 2020 at 7:37 PM Atita Arora <atitaar...@gmail.com> wrote: > > > Hi, > > > > I am working on improving the search app which is using 'qt' param > heavily > > to redirect requests to different handlers based on the parameters as > > provided by the user. > > > > Also for A B testing of different configurations, we have used qt param > to > > send request to different handlers. > > My question here is that on Solr 6.2.6 to enable using 'qt' param I need > to > > do handleSelect=false but it is the default request handler on solr > > administration UI and used as the default endpoint in all the integration > > tests. > > > > It may sound weird but is there a way I can retain both the > > functionalities? > > No code changes to integration test code and making qt param work again. > > > > Big thanks for any pointers !! > > > > Sincerely, > > Atita > > > > > -- > Sincerely yours > Mikhail Khludnev >
