pysolr should support custom handlers about pysolr HOT 10 CLOSED

Please see my fork for a patch (sorry, new to github - don't know how to open a pull request) llnik/pysolr@e65143b

With this, a custom handler "search" could be used like this

import pysolr
s = pysolr.Solr("localhost:8983/solr")
foo = s.search(q="bar", handler="search") # queries /solr/search instead of /solr/select
baz = s.search(q="bar").docs # queries /solr/select (default behaviour)

/Edit: [x] Pull request

from pysolr.

👍 shame this isn't in already, a basic piece of functionality IMO.

from pysolr.

@hamishcampbell If you have time to help to work on a pull-request, I think #52 might be a good starting point. If we can get a current patch and some tests it'll be a lot faster to merge

from pysolr.

As alternative, you can change back to "old" SOLR behavior:

1. Set the RequestDispatcher to handleSelect="true" (default is false since 3.6).
   See https://wiki.apache.org/solr/SolrRequestHandler#Old_handleSelect.3Dtrue_Resolution_.28qt_param.29
2. rename your current /select request handler and add the attribute default="true"
3. add the qt parameter to your queries: qt=/myhandler (you can leave the slashes but the request handlers won't be accessible via path variable). The value of the qt variable is exactly the value of the name attribute.

Example solrconfig.xml (extract):

<requestDispatcher handleSelect="true" >
    <!-- Make sure your system has some authentication! before using enableRemoteStreaming="true" -->
    <requestParsers enableRemoteStreaming="true" multipartUploadLimitInKB="2048000" />

    <httpCaching lastModifiedFrom="openTime" etagSeed="Solr" />
    <httpCaching never304="true"/>
</requestDispatcher>

<requestHandler name="/myhandler" class="solr.SearchHandler" default="true">
    <lst name="defaults">
        <str name="defType">edismax</str>
        <str name="echoParams">explicit</str>
        <str name="q.op">AND</str>
        ...
    </lst>
</requestHandler>

from pysolr.

@toastdriven @acdha Are you still actively merging pull requests? Can we please get some of these patches merged in or explanation as to why they were rejected? Thank you!

from pysolr.

@mbeacom If you need either of these, the first place to start would be updating the code against the current branch to confirm that there are no test regressions. I work on pysolr in my spare time so anything which makes review easier is going to help.

from pysolr.

@acdha I am not trying to add more work for you. I'll go ahead and get it up to speed. Thank you!

from pysolr.

@acdha #161

from pysolr.

I've rebased (again) onto the current master (pull request #134). Is there a problem or are there considerations that prevent you from merging this? We are using this in production without issues, so far.

from pysolr.

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

from pysolr.