lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Simon Willnauer (JIRA)" <>
Subject [jira] [Created] (LUCENE-4524) Merge DocsEnum and DocsAndPositionsEnum into PostingsEnum
Date Thu, 01 Nov 2012 22:50:13 GMT
Simon Willnauer created LUCENE-4524:

             Summary: Merge DocsEnum and DocsAndPositionsEnum into PostingsEnum
                 Key: LUCENE-4524
             Project: Lucene - Core
          Issue Type: Improvement
          Components: core/codecs, core/index, core/search
    Affects Versions: 4.0
            Reporter: Simon Willnauer
             Fix For: 4.1, 5.0

spinnoff from

hey folks, 

I have spend a hell lot of time on the positions branch to make 
positions and offsets working on all queries if needed. The one thing 
that bugged me the most is the distinction between DocsEnum and 
DocsAndPositionsEnum. Really when you look at it closer DocsEnum is a 
DocsAndFreqsEnum and if we omit Freqs we should return a DocIdSetIter. 
Same is true for 
DocsAndPostionsAndPayloadsAndOffsets*YourFancyFeatureHere*Enum. I 
don't really see the benefits from this. We should rather make the 
interface simple and call it something like PostingsEnum where you 
have to specify flags on the TermsIterator and if we can't provide the 
sufficient enum we throw an exception? 
I just want to bring up the idea here since it might simplify a lot 
for users as well for us when improving our positions / offset etc. 

thoughts? Ideas? 


This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

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

View raw message