lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Muir (JIRA)" <>
Subject [jira] [Updated] (LUCENE-4088) unindexed (stored-only) fields prevent future indexing of offsets
Date Tue, 29 May 2012 22:38:23 GMT


Robert Muir updated LUCENE-4088:

    Attachment: LUCENE-4088.patch

same patch but with cosmetic fixes: the writeFreq/writeProx etc in FreqProxTermsWriter was
imo confusing, especially as in flush its assigned to readFreq/readProx etc. I think these
are clearer as hasFreq/hasProx.

I think this one is ready to commit
> unindexed (stored-only) fields prevent future indexing of offsets
> -----------------------------------------------------------------
>                 Key: LUCENE-4088
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Bug
>          Components: core/index
>            Reporter: Robert Muir
>             Fix For: 4.0
>         Attachments: LUCENE-4088.patch, LUCENE-4088.patch, LUCENE-4088.patch
> this is because we bogusly set FieldInfo.indexOptions to DOCS_AND_FREQS_AND_POSITIONS
if the field is stored-only.
> I don't think we should do that: the indexOptions should be null.

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


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

View raw message