[
https://issues.apache.org/jira/browse/SOLR-7090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14944094#comment-14944094
]
Scott Blum edited comment on SOLR-7090 at 10/5/15 9:37 PM:
-----------------------------------------------------------
I have this basically working as a QParser. Under the hood, it uses a
distributed Facet query to collect the appropriate term list, which it then
applies to the local core.
The main test works, but the random tests I'm having trouble with, and I'm not
sure what I'm doing wrong. I'm getting a different set of failures on trunk
than I was getting on a similar patch against ~5.2.1.
On trunk, the final result set tends to have too few documents in it, (e.g. 10
!= 7), even though the fulljoin is actually recording that it found 10 docs.
I've been digging on this but haven't figured it out yet.
On ~5.2.1, I was getting a different failure related to caching. On index
clear + commit, a fulljoin query result would get cached, and subsequent
commits would not invalidate the result, so by the time a query would be
performed, it would miss all but the first few docs.
Any help would be much appreciated!
was (Author: dragonsinth):
I have this basically working as a QParser. Under the hood, it uses a
distributed Facet query to collect the appropriate term list, when it then
applies to the local core.
I can't get all the random tests to work, though, and I'm not sure what I'm
doing wrong. I'm getting a different set of failures on trunk than I was
getting on a similar patch against ~5.2.1.
On trunk, the final result set tends to have too few documents in it, (e.g. 10
!= 7), even though the fulljoin is actually recording that it found 10 docs.
I've been digging on this but haven't figured it out yet.
On ~5.2.1, I was getting a different failure related to caching. On index
clear + commit, a fulljoin query result would get cached, and subsequent
commits would not invalidate the result, so by the time a query would be
performed, it would miss all but the first few docs.
Any help would be much appreciated!
> Cross collection join
> ---------------------
>
> Key: SOLR-7090
> URL: https://issues.apache.org/jira/browse/SOLR-7090
> Project: Solr
> Issue Type: New Feature
> Reporter: Ishan Chattopadhyaya
> Fix For: 5.2, Trunk
>
> Attachments: SOLR-7090-fulljoin.patch, SOLR-7090.patch
>
>
> Although SOLR-4905 supports joins across collections in Cloud mode, there are
> limitations, (i) the secondary collection must be replicated at each node
> where the primary collection has a replica, (ii) the secondary collection
> must be singly sharded.
> This issue explores ideas/possibilities of cross collection joins, even
> across nodes. This will be helpful for users who wish to maintain boosts or
> signals in a secondary, more frequently updated collection, and perform query
> time join of these boosts/signals with results from the primary collection.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
