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 21:15:47 GMT


Michael McCandless commented on LUCENE-3133:

I'm confused on why the query parser language would need to be
extended to handle this...

Ie, it seems like, for a given index, the assignment of fields to
parent vs child docs is a global/static decision?  And then any query
that has clauses against mixed parent/child fields should be "wrapped"
by NestedDocumentQuery so that the child field/doc matches are
"translated" to the corresponding parent docs?

Why should each query be free to change this?

EG if a user type that same query, but without WITH, then nothing
would match right?

I guess this means I'd vote for 2 :)

> 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