[
https://issues.apache.org/jira/browse/LUCENE-2016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12771533#action_12771533
]
Robert Muir edited comment on LUCENE-2016 at 10/29/09 6:23 PM:
---------------------------------------------------------------
bq. Tricky semantics It rather depends on if you consider Lucene part if your
"process-internally" . Depending on the use case, it could be either.
Not really, Lucene-java uses U+FFFF process-internally, but wasn't mapping it
to something valid in the index. So when U+FFFF was stored in the index (or
rather, wasn't being stored but handled incorrectly), it created an issue. This
is a perfect example of this.
was (Author: rcmuir):
bq. Tricky semantics It rather depends on if you consider Lucene part if
your "process-internally" . Depending on the use case, it could be either.
Not really, Lucene-java uses U+FFFF process-internally, but wasn't mapping it
to something valid in the index. So when U+FFFF was stored in the index, it
created an issue. This is a perfect example of this.
> replace invalid U+FFFF character during indexing
> ------------------------------------------------
>
> Key: LUCENE-2016
> URL: https://issues.apache.org/jira/browse/LUCENE-2016
> Project: Lucene - Java
> Issue Type: Bug
> Affects Versions: 2.4, 2.4.1, 2.9
> Reporter: Michael McCandless
> Assignee: Michael McCandless
> Fix For: 2.9.1, 3.0
>
> Attachments: LUCENE-2016.patch
>
>
> If the invalid U+FFFF character is embedded in a token, it actually causes
> indexing to silently corrupt the index by writing duplicate terms into the
> terms dict. CheckIndex will catch the error, and merging will hit exceptions
> (I think).
> We already replace invalid surrogate pairs with the replacement character
> U+FFFD, so I'll just do the same with U+FFFF.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
