[LUCENE-4524] Merge DocsEnum and DocsAndPositionsEnum into PostingsEnum

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 4.0
• Fix Version/s: 5.1, 6.0
• Component/s: core/codecs, core/index, core/search
• Lucene Fields: New
• Assignee: Alan Woodward
• Reporter: Simon Willnauer
• Created: 01/Nov/12 22:49
• Updated: 28/Aug/22 13:31
• Resolved: 06/Feb/15 16:40

Description

spinnoff from http://www.gossamer-threads.com/lists/lucene/java-dev/172261

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. 
support. 

thoughts? Ideas? 

simon 

Issue Links

• is related to: LUCENE-2878 Allow Scorer to expose positions and payloads aka. nuke spans