[ 
https://issues.apache.org/jira/browse/LUCENE-3759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15050253#comment-15050253
 ] 

Ashish Datta commented on LUCENE-3759:
--------------------------------------

Hi guys,
Is this issue being addressed in a future release etc. ?
In order that Solr/Lucene be able to horizontally shard and yet give a unified 
view to queries that need to access joined data, I think this will be a BIG hit 
!
I saw a similar thing in the Mongo system where a 'queryrouter' did the same 
job of sending parallel query requests to multiple servers with individual 
shards and returned a consistent result. Though the two tools are entirely 
different, if the data/facets distribution and shard keying is known, this does 
not seem unsurmountable in Lucene. 
Would be really interested and eager to provide a use case in an actual 
production scenario where the lack of this feature is causing some grief ! and 
increasing the query coding to compensate for it. 

> Support joining in a distributed environment.
> ---------------------------------------------
>
>                 Key: LUCENE-3759
>                 URL: https://issues.apache.org/jira/browse/LUCENE-3759
>             Project: Lucene - Core
>          Issue Type: Improvement
>          Components: modules/join
>            Reporter: Martijn van Groningen
>
> Add two more methods in JoinUtil to support joining in a distributed manner.
> * Method to retrieve all from values.
> * Method to create a TermsQuery based on a set of from terms.
> With these two methods distributed joining can be supported following these 
> steps:
> # Retrieve from values from each shard
> # Merge the retrieved from values. 
> # Create a TermsQuery based on the merged from terms and send this query to 
> all shards. 



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

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to