lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Muir (Updated) (JIRA)" <>
Subject [jira] [Updated] (LUCENE-3529) creating empty field + empty term leads to invalid index
Date Mon, 24 Oct 2011 18:46:32 GMT


Robert Muir updated LUCENE-3529:

    Attachment: LUCENE-3529_test.patch

attached is a test (committed to trunk).

I also fixed the assert and removed the bogus check in Field's ctor.

But the checkIndex fails (as it does before, if you index this term with assertions disabled).
So next step is to figure out a fix...
> creating empty field + empty term leads to invalid index
> --------------------------------------------------------
>                 Key: LUCENE-3529
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Bug
>    Affects Versions: 3.4
>            Reporter: Robert Muir
>         Attachments: LUCENE-3529_test.patch
> Spinoff from LUCENE-3526.
> * if you create new Field("", ""), you get IllegalArgumentException from Field's ctor:
"name and value cannot both be empty"
> * But there are tons of other ways to index an empty term for the empty field (for example
initially make it "garbage" then .setValue(""), or via tokenstream).
> * If you do this, and you have assertions enabled, you will trip an assert (the assert
is fixed in trunk, in LUCENE-3526)
> * But If you don't have assertions enabled, you will create a corrupt index: test: terms,
freq, prox...ERROR [term : docFreq=1 != num docs seen 0 + num docs deleted 0]

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