[
https://issues.apache.org/jira/browse/SOLR-4970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13694728#comment-13694728
]
Shalin Shekhar Mangar commented on SOLR-4970:
---------------------------------------------
You need to generate a patch against trunk before anyone will review it. See
http://wiki.apache.org/solr/HowToContribute
But before we go any further, can you describe your solution? It sounds like
you join on unique-keys between two different solr collections? How well does
it perform? Why do you need to extend SolrDispatchFilter and why does it need a
custom JSON response writer?
It sounds like your solution works on top of Solr instead of integrating with
solr internals. If it is the former than it would be difficult to ship it with
Solr.
> 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
> Attachments: collectioncomm.zip
>
>
> 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]
