[
https://issues.apache.org/jira/browse/LUCENE-3526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13134083#comment-13134083
]
Robert Muir commented on LUCENE-3526:
-------------------------------------
There are more serious problems in 3.x here.
* 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 the same
assert bug i fixed in trunk here.
* 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]
So we need to figure out what the semantics should be for 3.x. is Term("", "")
allowed or not?
> preflex codec returns wrong terms if you use an empty field name
> ----------------------------------------------------------------
>
> Key: LUCENE-3526
> URL: https://issues.apache.org/jira/browse/LUCENE-3526
> Project: Lucene - Java
> Issue Type: Bug
> Affects Versions: 4.0
> Reporter: Robert Muir
> Attachments: LUCENE-3526.patch, LUCENE-3526_test.patch,
> LUCENE-3526_test.patch, LUCENE-3526_test.patch, LUCENE-3526_test.patch
>
>
> spinoff from LUCENE-3473.
> I have a standalone test for this... the termsenum is returning a bogus extra
> empty-term (I assume it has no postings, i didnt try).
> This causes the checkindex test in LUCENE-3473 to fail, because there are 4
> terms instead of 3.
--
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]
