lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Harwood (JIRA)" <>
Subject [jira] [Commented] (LUCENE-2454) Nested Document query support
Date Tue, 24 May 2011 09:00:49 GMT


Mark Harwood commented on LUCENE-2454:

Thanks for the patch work, Mike. I'll need to check LUCENE-3129 for equivalence with PerParentLimitQuery.
It's certainly a central part of what I typically deploy for nested queries - pass 1 is usually
a NestedDocumentQuery to get the best parents and pass 2 uses PerParentLimitQuery to get the
best children for these best parents. Of course some apps can simply fetch ALL children for
the top parents but in some cases summarising children is required (note: this is potentially
a great solution for performance issues on highlighting big docs e.g. entire books).

I haven't benchmarked nextSetBit vs the existing "rewind" implementation but I imagine it
may be quicker. Parent- followed-by-children seems more natural from a user's point of view
however. I guess you could always keep the parent-then-child insertion order but flip the
bitset (then cache) for query execution if that was faster. Benchmarking rewind vs nextSetbit
vs flip then nextSetBit would reveal all.

Thomas - maintaining a strict order of parent/child docs is important and the recently-committed
LUCENE-3112 should help with this.

> Nested Document query support
> -----------------------------
>                 Key: LUCENE-2454
>                 URL:
>             Project: Lucene - Java
>          Issue Type: New Feature
>          Components: core/search
>    Affects Versions: 3.0.2
>            Reporter: Mark Harwood
>            Assignee: Mark Harwood
>            Priority: Minor
>         Attachments: LUCENE-2454.patch,
> A facility for querying nested documents in a Lucene index as outlined in

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