lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Harwood (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LUCENE-3133) Fix QueryParser to handle nested fields
Date Mon, 23 May 2011 22:11:47 GMT

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

Mark Harwood commented on LUCENE-3133:
--------------------------------------

So the 2 reasons I can think of why the WITH construct may be needed are:
1) If the field names aren't exclusive to a doc type e.g. "name" or "age" is a field found
on both parent and child docs
or
2) If you want to find a parent with two different children (e.g. a resume of someone who
has held a position at Google in 2009 and a different position at LinkedIn during 2010).

In both cases the WITH clause is needed to set the context around clauses to avoid any ambiguity

> Fix QueryParser to handle nested fields
> ---------------------------------------
>
>                 Key: LUCENE-3133
>                 URL: https://issues.apache.org/jira/browse/LUCENE-3133
>             Project: Lucene - Java
>          Issue Type: Improvement
>            Reporter: Michael McCandless
>             Fix For: 3.2, 4.0
>
>
> Once we commit LUCENE-2454, we need to make it easy for apps to enable this with QueryParser.
> It seems like it's a "schema" like behavior, ie we need to be able to express the join
structure of the related fields.
> And then whenever QP produces a query that spans fields requiring a join, the NestedDocumentQuery
is used to wrap the child fields?

--
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