Hello,
I am writing this question in reference to the stackoverflow question
http://stackoverflow.com/questions/39596832/solrj-not-setting-request-handler.
There were no solutions there and it was recommended that I email this list for
a possible solution. See that question for screenshots and another description
of what is going on.
Basically, I have a SolrCloud (Solr 6.0.1) collection set up with multiple
request handlers. This SolrCloud instance is the result of a cloud migration
from a standalone Solr instance (5.3.0). Both of these Solr instances have
similar indices (I think some field names may have changed in the cloud
version, but that shouldn't be a big deal here) with identical request
handlers. In the standalone version, I could query the request handler "all"
in SolrJ by using SolrQuery.setRequestHandler("/all"). Other request handlers
worked the same way. As you probably know, all setRequestHandler does is set
qt=/all and calls select to handle this.
However, in the cloud version, the setRequestHandler method yields no results.
Any queries with qt=/all give a NullPointerException in
QueryComponent.mergeIds(line 1059). This points to there being an issue with
the all RequestHandler, but, interestingly enough, querying Solr via a browser,
using http://solrIP:port/collection/all?q=term works fine. Removing the /
results in the RequestHandler not being found and the /select handler being
used. Similar behavior is observed for the other RequestHandlers that we have
defined.
The /select handler has only the default xml in solrconfig.xml.
Does anyone know what I could do to get these request handlers to work via qt?
Thank you,
Jared Moore
IT Developer
Search and Personalization
The Home Depot
Work: 404.394.5910
Mobile: 603.833.1793
jared_mo...@homedepot.com
________________________________
The information in this Internet Email is confidential and may be legally
privileged. It is intended solely for the addressee. Access to this Email by
anyone else is unauthorized. If you are not the intended recipient, any
disclosure, copying, distribution or any action taken or omitted to be taken in
reliance on it, is prohibited and may be unlawful. When addressed to our
clients any opinions or advice contained in this Email are subject to the terms
and conditions expressed in any applicable governing The Home Depot terms of
business or client engagement letter. The Home Depot disclaims all
responsibility and liability for the accuracy and content of this attachment
and for any damages or losses arising from any inaccuracies, errors, viruses,
e.g., worms, trojan horses, etc., or other items of a destructive nature, which
may be contained in this attachment and shall not be liable for direct,
indirect, consequential or special damages in connection with this e-mail
message or its attachment.
________________________________
The information in this Internet Email is confidential and may be legally
privileged. It is intended solely for the addressee. Access to this Email by
anyone else is unauthorized. If you are not the intended recipient, any
disclosure, copying, distribution or any action taken or omitted to be taken in
reliance on it, is prohibited and may be unlawful. When addressed to our
clients any opinions or advice contained in this Email are subject to the terms
and conditions expressed in any applicable governing The Home Depot terms of
business or client engagement letter. The Home Depot disclaims all
responsibility and liability for the accuracy and content of this attachment
and for any damages or losses arising from any inaccuracies, errors, viruses,
e.g., worms, trojan horses, etc., or other items of a destructive nature, which
may be contained in this attachment and shall not be liable for direct,
indirect, consequential or special damages in connection with this e-mail
message or its attachment.
