lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yonik Seeley (JIRA)" <>
Subject [jira] Commented: (LUCENE-2831) Revise Weight#scorer & Filter#getDocIdSet API to pass Readers context
Date Wed, 05 Jan 2011 17:40:49 GMT


Yonik Seeley commented on LUCENE-2831:

I'm browsing through this latest patch a bit...
- ReaderContextBuilder.numLeafes uses an AtomicInt, but ReaderUtil.Gather doesn't do any threading.
- ReaderContext.leaves() is a method - shouldn't it just be a member for consistency?  I don't
really understand the javadoc on that method either, since I don't see how I could walk the
tree myself - there are no child pointers.
- Is ReaderContext.isTopLevel redundant (i.e. it will always be equal to parent==null)?  Maybe
the same thing for isAtomic and leaves==null?

> Revise Weight#scorer & Filter#getDocIdSet API to pass Readers context
> ---------------------------------------------------------------------
>                 Key: LUCENE-2831
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Improvement
>          Components: Search
>    Affects Versions: 4.0
>            Reporter: Simon Willnauer
>            Assignee: Simon Willnauer
>             Fix For: 4.0
>         Attachments: LUCENE-2831.patch, LUCENE-2831.patch, LUCENE-2831.patch, LUCENE-2831.patch
> Spinoff from LUCENE-2694 - instead of passing a reader into Weight#scorer(IR, boolean,
boolean) we should / could revise the API and pass in a struct that has parent reader, sub
reader, ord of that sub. The ord mapping plus the context with its parent would make several
issues way easier. See LUCENE-2694, LUCENE-2348 and LUCENE-2829 to name some.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

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

View raw message