[
https://issues.apache.org/jira/browse/SOLR-303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley updated SOLR-303:
------------------------------
Attachment: distributed.patch
OK, this version patches cleanly and includes some distributed faceting code.
- facet.query and facet.field sorted by count is mostly handled
- breaking ties by natural (index) sort order is not yet implemented
- date faceting and unsorted (index order) facet.field is not implemented
Assuming the user asks for the top 10 terms of a field:
1) The first facet queries piggyback on the queries to get the top ids and sort
field values.
2) counts are merged, and new "refinement" requests are send out for those
terms in the top 10 where a count was not received from some shards. Also, for
terms below the top 10, we calculate the maximum it could have based on shards
we have not heard from, and if that boosts it into the top 10, we include that
term for "refinement".
3) refinement responses are used to adjust the counts, and we are done.
Note that it is theoretically possible to miss terms. A term could be just
below the threshold of each shard (and thus not returned by any shard), but the
total count could boost it in the top. This could be rectified by retrieving
*all* terms above a specified count, but it could be expensive. The counts
that are currently returned are exact.
> 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, 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.
