[
https://issues.apache.org/jira/browse/SOLR-4970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13694653#comment-13694653
]
Jilani Shaik commented on SOLR-4970:
------------------------------------
The implementation which we did is contrib approach. Created a new contrib
structure as "collectioncomm" with a extended "SolrDispacthFilter" and custom
JSON response writer.
> Collection communication for merging the facet query result from one
> collection to other collection
> ---------------------------------------------------------------------------------------------------
>
> Key: SOLR-4970
> URL: https://issues.apache.org/jira/browse/SOLR-4970
> Project: Solr
> Issue Type: New Feature
> Components: SearchComponents - other
> Reporter: Jilani Shaik
> Priority: Minor
> Labels: features
>
> Scenario:
> We will have two categories of data, where one category will be the list of
> primary data (for example products) and the other collection (it could be
> spread across shards) holds the transaction data (for example product sales
> data). We have a search scenario where we need to show the products along
> with the number of sales for each product.
> We can do flatten the schema with all data together, But if the primary
> data(it could be very less may be <10000) should be in one collection where
> as the transaction data(it could be in millions) in multiple shards, then we
> wish to have this feature where the request handler will search the data from
> one collection and the corresponding search results docs should pass to the
> next query for faceting and then before writing the response merge these
> together to appear the result as coming from one collection.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
