On 6/12/2015 1:02 PM, Steven White wrote:
> You are right. If I use "solr.SearchHandler" it works, but if I
> use "solr.admin.AdminHandlers" like so:
>
> <requestHandler name="987" class="solr.admin.AdminHandlers">
> </requestHandler>
>
> Solr reports this error:
>
> HTTP ERROR 500
>
> Problem accessing /solr/db/config/requestHandler. Reason:
>
> {msg=SolrCore 'db' is not available due to init failure: The
> AdminHandler needs to be registered to a path. Typically this is
With an admin handler, it won't be possible to access that handler if
it's not a path that starts with a slash, so it can be incorporated into
the request URL. Solr is making sure the config will work, and throwing
an error when it won't work.
With search handlers, if you set up the config right, you *CAN* access
that handler through a request parameter on the /select handler, it does
not need to be part of the URL path. The default config found in
examples for 4.x and later will prevent that from working, but you can
change the config to allow it ... so search handlers must work even if
the name is not a path. The config validation is not as strict as it is
for an admin handler.
Thanks,
Shawn
