[jira] [Comment Edited] (SOLR-4905) Cross core joins don't work for SolrCloud collections and/or aliases
[ https://issues.apache.org/jira/browse/SOLR-4905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14049570#comment-14049570 ] Jack Lo edited comment on SOLR-4905 at 7/2/14 3:19 AM: --- I have noticed this issue have been lying around for a year, seems like nobody is bother to use JOIN in solrcloud, so I decide to tackle this myself. A small patch has been uploaded here to allow fromIndex to specify a collection under cloud environment. Currently, it works if the fromIndex collection is a single shard having at least 1 replica on each node. I am planning to support multi-shard collection but not really sure how to do it given I am not that familiar with the internal mechanics of solr. Even if we support multishard, given the current implementation of JoinQParser, I think we can only support it when a collection with at least 1 replica of all shards physically residing on every node. We need all local IndexSearcher. If we need full solrcloud join support, I think we need to revamp JoinQParser or make something on a higher level to gather terms collection from remote shards on StandardRequestHandler. By the way, I noticed we haven't use JoinUtil in LUCENE, is there a reason to not use it, their implementation seems to be more cleaner than the one in SOLR right now, I have no idea what it's doing in JoinQParser was (Author: jacklo): Partially make solrcloud join to work Cross core joins don't work for SolrCloud collections and/or aliases Key: SOLR-4905 URL: https://issues.apache.org/jira/browse/SOLR-4905 Project: Solr Issue Type: Improvement Components: SolrCloud Reporter: Philip K. Warren Attachments: patch.txt Using a non-SolrCloud setup, it is possible to perform cross core joins (http://wiki.apache.org/solr/Join). When testing with SolrCloud, however, neither the collection name, alias name (we have created aliases to SolrCloud collections), or the automatically generated core name (i.e. collection_shard1_replica1) work as the fromIndex parameter for a cross-core join. -- This message was sent by Atlassian JIRA (v6.2#6252) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Comment Edited] (SOLR-4905) Cross core joins don't work for SolrCloud collections and/or aliases
[ https://issues.apache.org/jira/browse/SOLR-4905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14049570#comment-14049570 ] Jack Lo edited comment on SOLR-4905 at 7/2/14 3:21 AM: --- I have noticed this issue have been lying around for a year, seems like nobody is bother to use JOIN in solrcloud, so I decide to tackle this myself. A small patch has been uploaded here to allow fromIndex to specify a collection under cloud environment. Currently, it works if the fromIndex collection is a single shard having at least 1 replica on each node. I am planning to support multi-shard collection but not really sure how to do it given I am not that familiar with the internal mechanics of solr. Even if we support multishard, given the current implementation of JoinQParser, I think we can only support it when a collection with at least 1 replica of all shards physically residing on every node. We need all local IndexSearcher. If we need full solrcloud join support, I think we need to revamp JoinQParser or make something on a higher level to gather terms collection from remote shards on StandardRequestHandler. By the way, I noticed we haven't use JoinUtil in LUCENE, is there a reason to not use it, their implementation seems to be more cleaner than the one in SOLR right now, I have no idea how JoinQParser works, especally the getdocset stage. was (Author: jacklo): I have noticed this issue have been lying around for a year, seems like nobody is bother to use JOIN in solrcloud, so I decide to tackle this myself. A small patch has been uploaded here to allow fromIndex to specify a collection under cloud environment. Currently, it works if the fromIndex collection is a single shard having at least 1 replica on each node. I am planning to support multi-shard collection but not really sure how to do it given I am not that familiar with the internal mechanics of solr. Even if we support multishard, given the current implementation of JoinQParser, I think we can only support it when a collection with at least 1 replica of all shards physically residing on every node. We need all local IndexSearcher. If we need full solrcloud join support, I think we need to revamp JoinQParser or make something on a higher level to gather terms collection from remote shards on StandardRequestHandler. By the way, I noticed we haven't use JoinUtil in LUCENE, is there a reason to not use it, their implementation seems to be more cleaner than the one in SOLR right now, I have no idea what it's doing in JoinQParser Cross core joins don't work for SolrCloud collections and/or aliases Key: SOLR-4905 URL: https://issues.apache.org/jira/browse/SOLR-4905 Project: Solr Issue Type: Improvement Components: SolrCloud Reporter: Philip K. Warren Attachments: patch.txt Using a non-SolrCloud setup, it is possible to perform cross core joins (http://wiki.apache.org/solr/Join). When testing with SolrCloud, however, neither the collection name, alias name (we have created aliases to SolrCloud collections), or the automatically generated core name (i.e. collection_shard1_replica1) work as the fromIndex parameter for a cross-core join. -- This message was sent by Atlassian JIRA (v6.2#6252) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Comment Edited] (SOLR-4905) Cross core joins don't work for SolrCloud collections and/or aliases
[
https://issues.apache.org/jira/browse/SOLR-4905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13737585#comment-13737585
]
Utkarsh Sengar edited comment on SOLR-4905 at 8/13/13 12:09 AM:
@Chris I have solrcloud 4.4 running with 3 shards and 2 cores. A cross-core
join does not work even when cores are created during the bootstrap time.
This is my query:
{noformat} http://SOLR_SERVER/solr/merchant/select?q={!join from=merchantId
to=merchantId fromIndex=deals}apple {noformat}
This query returns no documents, full response with debugQuery=true:
http://apaste.info/uHOw
But both of my cores have a common merchantId when I query for apple. So I
think this problem is a general problem in solrcloud.
was (Author: zengr):
@Chris I have solrcloud 4.4 running with 3 shards and 2 cores. A cross-core
join does not work even when cores are created during the bootstrap time.
This is my query:
http://SOLR_SERVER/solr/merchant/select?q={!join from=merchantId to=merchantId
fromIndex=deals}apple
This query returns no documents, full response with debugQuery=true:
http://apaste.info/uHOw
But both of my cores have a common merchantId when I query for apple. So I
think this problem is a general problem in solrcloud.
Cross core joins don't work for SolrCloud collections and/or aliases
Key: SOLR-4905
URL: https://issues.apache.org/jira/browse/SOLR-4905
Project: Solr
Issue Type: Improvement
Components: SolrCloud
Reporter: Philip K. Warren
Using a non-SolrCloud setup, it is possible to perform cross core joins
(http://wiki.apache.org/solr/Join). When testing with SolrCloud, however,
neither the collection name, alias name (we have created aliases to SolrCloud
collections), or the automatically generated core name (i.e.
collection_shard1_replica1) work as the fromIndex parameter for a
cross-core join.
--
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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
