[
https://issues.apache.org/jira/browse/LUCENE-3684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13186331#comment-13186331
]
Simon Willnauer commented on LUCENE-3684:
-----------------------------------------
do we really need {code}static final int FORMAT_CURRENT =
FORMAT_OFFSETS_IN_POSTINGS;{code} I mean the FORMAT_FLEX was introduced with
flexible indexing and since we didn't release since then I think its confusing.
We already changed this format since flex (ie. DocValues) without adding a new
format. In LUCENE-3687 I separated the 3x and 4.0 format and removed all the
previous formats from 4.0 I think this code should start with a min3xFormat-1.
> Add offsets to postings (D&PEnum)
> ---------------------------------
>
> Key: LUCENE-3684
> URL: https://issues.apache.org/jira/browse/LUCENE-3684
> Project: Lucene - Java
> Issue Type: Improvement
> Reporter: Michael McCandless
> Assignee: Michael McCandless
> Fix For: 4.0
>
> Attachments: LUCENE-3684.patch, LUCENE-3684.patch
>
>
> I think should explore making start/end offsets a first-class attr in the
> postings APIs, and fixing the indexer to index them into postings.
> This will make term vector access cleaner (we now have to jump through
> hoops w/ non-first-class offset attr). It can also enable efficient
> highlighting without term vectors / reanalyzing, if the app indexes
> offsets into the postings.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
