[
https://issues.apache.org/jira/browse/LUCENE-3133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13038235#comment-13038235
]
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: 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-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
