lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From András Péteri (JIRA) <>
Subject [jira] [Commented] (LUCENE-3854) Non-tokenized fields become tokenized when a document is deleted and added back
Date Tue, 12 Jun 2012 08:25:44 GMT


András Péteri commented on LUCENE-3854:

Isn't this considered a regression from 3.x? In 3.6.0 I'm seeing an additional byte being
read from the stream in FieldsReader, which contained bits that allowed the reader to reconstruct
the Index enum correctly for the field. This should make it possible to properly update a
document in which all fields were stored, with the exception of boost values (and they could
be stored redundantly in a field as well to overcome this limitation).
> Non-tokenized fields become tokenized when a document is deleted and added back
> -------------------------------------------------------------------------------
>                 Key: LUCENE-3854
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Bug
>          Components: core/index
>    Affects Versions: 4.0
>            Reporter: Benson Margulies
> is a JUnit test case that seems to
show a problem with the current trunk. It creates a document with a Field typed as StringField.TYPE_STORED
and a value with a "-" in it. A TermQuery can find the value, initially, since the field is
not tokenized.
> Then, the case reads the Document back out through a reader. In the copy of the Document
that gets read out, the Field now has the tokenized bit turned on. 
> Next, the case deletes and adds the Document. The 'tokenized' bit is respected, so now
the field gets tokenized, and the result is that the query on the term with the - in it no
longer works.
> So I think that the defect here is in the code that reconstructs the Document when read
from the index, and which turns on the tokenized bit.
> I have an ICLA on file so you can take this code from github, but if you prefer I can
also attach it here.

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