[
https://issues.apache.org/jira/browse/SOLR-303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12554524
]
Ryan McKinley commented on SOLR-303:
------------------------------------
{quote}
\\
For #3, are there SolrJ parts (or future parts) that we wouldn't want
automatically bundled with Solr?
\\
\\
{quote}
I don't think so. The thing I want to make sure is still possible is that
solrj can be distributed independently (without the lucene dependencies)
The existing artifact topology makes sense as is: common, solrj, core.
Currently we have:
{code}
+ common
+ solrj
+ core
{code}
we need
{code}
+ common
+ solrj
+core
{code}
or
{code}
+ common & solrj
+ core
{code}
This issue is essentially independent of SOLR-303, but we should try to make
our source directory structures consistent with standard practice.
{quote}
\\
Saving an if() doesn't seem too compelling (the current code could certainly be
refactored to be cleaner anyway). Are there other benefits to having a separate
DistributedSearchHandler though?
\\
\\
{quote}
If there is a good reason to keep it the *same* handler then that is a reason
enough.
I just looked at it (without really grocking how it works) and it seemed a bit
bloated with distribution lifecycle stuff. As long as the non-distributed
request cycle isn't tied to the distributed stuff, I'm sure it is fine.
-----
BTW, where does the term "shard" come from? What specifically does it refer to?
> 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.
