[
https://issues.apache.org/jira/browse/SOLR-303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12554513
]
Ryan McKinley commented on SOLR-303:
------------------------------------
I just took a quick look... a few observations:
We should extract out a few simple things and commit them quickly to make this
go more smoothly:
# move SearchHandler to o.a.s.handler.component -- I vote you go ahead and
commit that change.
# Create a separate issue for adding SolrDocument to XMLWriter
# Move solrj into the main source tree. I'm not sure the best way to do this,
but I don't think solrj should sit in its own source folder if the core depends
on it.
Is there a good reason to use the same handler for distributed search? Why not
have a DistributedSearchHandler that extends SearchHandler and skip the if {}
else {} checking? Likewise, I wonder if a DistributedResponseBuilder
could/should extend ResponseBuilding and add the necessary logic.
> Distributed Search over HTTP
> ----------------------------
>
> Key: SOLR-303
> URL: https://issues.apache.org/jira/browse/SOLR-303
> Project: Solr
> Issue Type: New Feature
> Components: search
> Reporter: Sharad Agarwal
> Assignee: Yonik Seeley
> Attachments: distributed.patch, distributed.patch, fedsearch.patch,
> fedsearch.patch, fedsearch.patch, fedsearch.patch, fedsearch.patch,
> fedsearch.patch, fedsearch.patch, fedsearch.stu.patch, fedsearch.stu.patch
>
>
> Searching over multiple shards and aggregating results.
> Motivated by http://wiki.apache.org/solr/DistributedSearch
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
