lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Briggs Thompson (JIRA)" <j...@apache.org>
Subject [jira] Issue Comment Edited: (SOLR-2272) Join
Date Thu, 24 Feb 2011 20:16:38 GMT

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

Briggs Thompson edited comment on SOLR-2272 at 2/24/11 8:15 PM:
----------------------------------------------------------------

>From the examples provided it doesn't look like this is possible but I just want to confirm
with you guys. It looks like all of the examples are joins on fields within the same schema,
but I am interested in joining on fields of a different schema (multiple core join).

I haven't played around with the join yet, but would the following be possible?

Core1
docId: int
body : text


Core2
id: int
docId : int


q={!join from=Core1.docId to=Core2.docId}Core1.body:"super" AND Core2.ID:[1 TO 10]

We have a similar use case to Tanguy Moal's example with one document type needs updating
more often than the other. I know we could store the Core2 ids in an array of integers in
Core1, but every time that ID mappings change we would have to re-index (with a potential
of constant re-indexing of nearly the same data).

Thanks for your help,
Briggs

      was (Author: briggs):
    From the examples provided it doesn't look like this is possible but I just want to confirm
with you guys. It looks like all of the examples are joins on fields within the same schema,
but I am interested in joining on fields of a different schema (multiple core join).

I haven't played around with the join yet, but would the following be possible?

Schema1
docId: int
body : text


Schema2
id: int
docId : int


q={!join from=Core1.docId to=Core2.docId}Core1.body:"super" AND Core2.ID:[1 TO 10]

We have a similar use case to Tanguy Moal's example with one document type needs updating
more often than the other. I know we could store the Core2 ids in an array of integers in
Core1, but every time that ID mappings change we would have to re-index (with a potential
of constant re-indexing of nearly the same data).

Thanks for your help,
Briggs
  
> Join
> ----
>
>                 Key: SOLR-2272
>                 URL: https://issues.apache.org/jira/browse/SOLR-2272
>             Project: Solr
>          Issue Type: New Feature
>          Components: search
>            Reporter: Yonik Seeley
>             Fix For: 4.0
>
>         Attachments: SOLR-2272.patch, SOLR-2272.patch
>
>
> Limited join functionality for Solr, mapping one set of IDs matching a query to another
set of IDs, based on the indexed tokens of the fields.
> Example:
> fq={!join  from=parent_ptr to:parent_id}child_doc:query

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message