ASF subversion and git services commented on LUCENE-6271:

Commit 79c2988547274612efd7ef589dc0afff76548640 in lucene-solr's branch 
refs/heads/master from [~dsmiley]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=79c2988 ]

LUCENE-6271: docs: TermsEnum.postings(...) will not return null

> PostingsEnum should have consistent flags behavior
> --------------------------------------------------
>                 Key: LUCENE-6271
>                 URL: https://issues.apache.org/jira/browse/LUCENE-6271
>             Project: Lucene - Core
>          Issue Type: Bug
>            Reporter: Ryan Ernst
>            Assignee: Robert Muir
>            Priority: Major
>             Fix For: 5.1
>         Attachments: LUCENE-6271.patch, LUCENE-6271.patch
> When asking for flags like OFFSETS or PAYLOADS with DocsAndPositionsEnum, the 
> behavior was to always return an enum, even if offsets or payloads were not 
> indexed.  They would just not be available from the enum if they were not 
> present.  This behavior was carried over to PostingsEnum, which is good.
> However, the new POSITIONS flag has different behavior.  If positions are not 
> available, null is returned, instead of a PostingsEnum that just gives access 
> to freqs.  This behavior is confusing, as it means you have to special case 
> asking for positions (only ask if you know they were indexed) which sort of 
> defeats the purpose of the unified PostingsEnum.
> We should make POSITIONS have the same behavior as other flags. The trickiest 
> part will be maintaining backcompat for DocsAndPositionsEnum in 5.x, but I 
> think it can be done.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to