You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Tom Winch (JIRA)" <ji...@apache.org> on 2015/12/10 18:01:11 UTC

[jira] [Issue Comment Deleted] (SOLR-8235) Federated Search (new) - Merge

     [ https://issues.apache.org/jira/browse/SOLR-8235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tom Winch updated SOLR-8235:
----------------------------
    Comment: was deleted

(was: patch against SOLR 4.10.3)

> Federated Search (new) - Merge
> ------------------------------
>
>                 Key: SOLR-8235
>                 URL: https://issues.apache.org/jira/browse/SOLR-8235
>             Project: Solr
>          Issue Type: New Feature
>            Reporter: Tom Winch
>            Priority: Minor
>              Labels: federated_search
>             Fix For: 4.10.3
>
>         Attachments: SOLR-8235.patch
>
>
> This issue describes a SearchComponent for merging search results obtained from a DJoin distributed search (see SOLR-8234) as part of federated search - that is, distributed search over documents stored in separated instances of SOLR (for example, one server per continent), where a single document (identified by an agreed, common unique id) may be stored in more than one server instance, with (possibly) differing fields and data.
> In the use of this search component, it is assumed that there is a single SOLR server (the "aggregator") that uses distributed search (shards=) to collect documents from other SOLR servers using DJoin (see SOLR-8234). The DJoin generates a result set containing parent documents each with child documents having the same unique id. This merge component turns each set of child documents into a single document conforming to the aggregator schema.
> For example, suppose the aggregator schema defines a multi-valued integer field, 'num', and three shards return field values "48", 23, and "strawberry". Then the resulting merged field value would be [48, 23] and an error would included for the NumberFormatException.
> Custom field merge behaviour may be specified by defining custom field types in the usual way and this is supported via a MergeAbstractFieldType class.
> This issue combines with others to provide full federated search support. See also SOLR-8234 and SOLR-8236.
> –
> Note that this is part of a new implementation of federated search as opposed to the older issues SOLR-3799 through SOLR-3805.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org