[ 
https://issues.apache.org/jira/browse/LUCENE-2694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Simon Willnauer updated LUCENE-2694:
------------------------------------

    Attachment: LUCENE-2694.patch

Another iteration on this after LUCENE-2831 was committed last week. 

 - updated to trunk & all test pass
- re-added all ord() related stuff back to TermsEnum since I think we should 
decouple this and solve it in a different issue. There is already enough 
changes in here and discussions should be focused on making MTQ single pass.
- Changed IndexSearcher to run concurrent searches on a "leaf slice" rather 
than on a leaf converted to a Top-Level Context. That made the callables a bit 
simpler and is more consistent since the hierarchy is preserved.
- TermState is now referenced by leaf ordinal and asserted using the leaf's 
top-level ctx.
- TermQuery is not single pass for all queries while state is only hold in 
Weight unless PerReaderTermState as not set. But even then the top-level ctx 
must be identical to the given IS's top-level ctx otherwise the give 
PerReaderTermState is not used.

this one seems pretty close 

> MTQ rewrite + weight/scorer init should be single pass
> ------------------------------------------------------
>
>                 Key: LUCENE-2694
>                 URL: https://issues.apache.org/jira/browse/LUCENE-2694
>             Project: Lucene - Java
>          Issue Type: Improvement
>          Components: Search
>            Reporter: Michael McCandless
>            Assignee: Simon Willnauer
>             Fix For: 4.0
>
>         Attachments: LUCENE-2694-FTE.patch, LUCENE-2694.patch, 
> LUCENE-2694.patch, LUCENE-2694.patch, LUCENE-2694.patch, LUCENE-2694.patch, 
> LUCENE-2694.patch, LUCENE-2694.patch
>
>
> Spinoff of LUCENE-2690 (see the hacked patch on that issue)...
> Once we fix MTQ rewrite to be per-segment, we should take it further and make 
> weight/scorer init also run in the same single pass as rewrite.

-- 
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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to