lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael McCandless (JIRA)" <>
Subject [jira] [Commented] (LUCENE-3133) Fix QueryParser to handle nested fields
Date Mon, 23 May 2011 22:35:47 GMT


Michael McCandless commented on LUCENE-3133:

Oh I see.  Hmm, is case 1 is going to cause problems?  (Ie if both parent & child docs
can come back matching a given field).  Is there a "normal" use case where you would want
to put same field name on both parent & child docs?  (I had thought normally the field
names would be orthogonal).

Case 2) I agree needs some special syntax.  In fact, even non-nested docs might want such
a query?  Eg if my docs are cars, and each car has a multi-valued field listing its features
("A/C", "Automatic transmission", ...), and I want to find all cars that have both A/C and
Automatic transmission.  Boolean AND query won't work correctly for this; I'd need this same
extension as your bullet 2 I think?

> Fix QueryParser to handle nested fields
> ---------------------------------------
>                 Key: LUCENE-3133
>                 URL:
>             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:

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

View raw message