lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Muir (JIRA)" <>
Subject [jira] Commented: (LUCENE-2019) map unicode process-internal codepoints to replacement character
Date Sat, 31 Oct 2009 02:50:59 GMT


Robert Muir commented on LUCENE-2019:

bq. Robert, you are a proponent of the (ICU)CollationKeyFilter functionality, which uses IndexableBinaryStringTools
to store arbitrary binary data in a Lucene index.

I'm actually only a fan of the idea of using unicode collation for searching and sorting.
as a default, binary comparison for most languages is absolute madness.

I'm not so much a fan of how it encodes this data binary data into what people expect to be
a character field, but I understand the limitations and don't blame the implementation :)
and this implementation never uses any of the characters in question, although thats not really

> map unicode process-internal codepoints to replacement character
> ----------------------------------------------------------------
>                 Key: LUCENE-2019
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Improvement
>          Components: Index
>            Reporter: Robert Muir
>            Priority: Minor
>         Attachments: LUCENE-2019.patch
> A spinoff from LUCENE-2016.
> There are several process-internal codepoints in unicode, we should not store these in
the index.
> Instead they should be mapped to replacement character (U+FFFD), so they can be used
> An example of this is how Lucene Java currently uses U+FFFF process-internally, it can't
be in the index or will cause problems. 

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:
For additional commands, e-mail:

View raw message