lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (LUCENE-6271) PostingsEnum should have consistent flags behavior
Date Tue, 31 Mar 2015 18:01:54 GMT


ASF subversion and git services commented on LUCENE-6271:

Commit 1670413 from [~rjernst] in branch 'dev/branches/lucene6271'
[ ]

LUCENE-6271: more nocommit removals for phrase/span term

> PostingsEnum should have consistent flags behavior
> --------------------------------------------------
>                 Key: LUCENE-6271
>                 URL:
>             Project: Lucene - Core
>          Issue Type: Bug
>            Reporter: Ryan Ernst
> 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:
For additional commands, e-mail:

View raw message