Ken Krugler 2011-12-15, 23:27
-Re: SearchComponents and ShardResponse
Chris Hostetter 2012-01-05, 00:40
: I feel like I must be missing something here...
: I'm working on a customized version of the SearchHandler, which supports
: distributed searching in multiple *local* cores.
: The SolrResponse field in ShardResponse is private, and the method to set it is package private.
: So it doesn't appear like there's any easy way to create the
: ShardResponse objects that the SearchComponents expect to receive inside
: of the ResponseBuilder.
I don't think you're missing anything. I think you're running into the
reality that the SearchHandler + SearchCOmponent + ResponseBuilder +
ShardResponse APIs haven't ever really been hammered on by many people
looking to build third-party distributed components outside of the solr
code base -- let alone trying to replace the SearchHandler itself with
their own versions, so it's not terribly suprising to me that you'd be
running into access limitations.
go ahead and open issues with the specific stuff you think should be made
public/protected -- but the usual caveats to that sort of thing apply of
course: need to audit everything to make sure we aren't letting
subclasses/clients stab us in the heart from the inside.
(I'm pretty sure i saw grant open an issue recently about trying to
clean up the APIs to make it easier to write distributed search components
... might wnat to follow up there as well)