lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mikhail Khludnev (JIRA)" <>
Subject [jira] [Commented] (SOLR-6033) LeftOuter Join capabilty in SOLR and dynamic field merge in response
Date Tue, 29 Apr 2014 14:27:24 GMT


Mikhail Khludnev commented on SOLR-6033:

it's a question to the mailing list, please close the issue.
you can "add" docs into result by specifying should clause

eg if you have q={!join from=p_id to=id}content:foo
you can do "left outer" like join by adding optional clause 
q=type:entity1 {!join from=p_id to=id}content:foo

> LeftOuter Join capabilty in SOLR and dynamic field merge in response
> --------------------------------------------------------------------
>                 Key: SOLR-6033
>                 URL:
>             Project: Solr
>          Issue Type: New Feature
>          Components: documentation, search
>    Affects Versions: 4.2.1, 4.3, 4.5.1, 4.6.1
>         Environment: RedHat Linux, 6GB Ram, Core2Duo Processor
>            Reporter: Kuntal Ganguly
>              Labels: build, feature, patch
>   Original Estimate: 72h
>  Remaining Estimate: 72h
> I'm having different kind of entity in the index.
> Entitity-1: id, doc_name, type, pinprojectid, documentid, content
> Entity-2: id, proj_name,projtype,type,pinprojectid
> where type is unique for every different entity e.g. Entity-1(type=Documents) & Entity-2(type=Projects).pinprojectid
is common between two Entity.
> Now im trying to search on type:Document AND content:"hello",
> but the result do left outer join with Entity-2 based on join field say ( pinprojectid)
and fetches few information like(projtype,proj_name) and display in the Entity-1 response.
> Say Entity-1 search gives 12 result,but left-outer join field fetch matches with 10 result.
> So the final output should be 12 with 10 doc containing extra merge fields through leftouter
> This is very common in SQL.
> One way to do this to process from client side with two separate call to SOLR server.But
this functaility or enhancement or added feature needs to there in solr release in a generalized
> Let me know if there is any other way to achieve the above scenario from server side
of Solr in one call??

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message