On Mon, Jan 31, 2011 at 9:22 PM, Chris Hostetter <hossman_luc...@fucit.org> wrote:
> that class should probably have been named ContentStreamUpdateHandlerBase > or something like that -- it tries to encapsulate the logic that most > RequestHandlers using COntentStreams (for updating) need to worry about. > > Your QueryComponent (as used by SearchHandler) should be able to access > the ContentStreams the same way that class does ... call > req.getContentStreams(). > > Sending a binary stream from a remote client depends on how the client is > implemented -- you can do it via HTTP using the POST body (with or w/o > multi-part mime) in any langauge you want. If you are using SolrJ you may > again run into an assumption that using ContentStreams means you are doing > an "Update" but that's just a vernacular thing ... something like a > ContentStreamUpdateRequest should work just as well for a query (as long > as you set the neccessary params and/or request handler path) Thanks for the help. I was just about to reply to my own question for the benefit of future googlers when I noticed your response. :) I actually got this working, much the way you suggest. The client is python. I created a gist with the script I used for testing [1]. On the solr side my QueryComponent grabs the stream, uses jzlib.ZInputStream to do the deflating, then translates the incoming integers in the bitset (my solr schema.xml integer ids) to the lucene ids and creates a docSetFilter with them. Very relieved to get this working as it's the basis of a talk I'm giving next week [2]. :-) --jay [1] https://gist.github.com/806397 [2] http://code4lib.org/conference/2011/luker
