lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yonik Seeley (JIRA)" <>
Subject [jira] Commented: (LUCENE-2019) map unicode process-internal codepoints to replacement character
Date Fri, 30 Oct 2009 22:39:59 GMT


Yonik Seeley commented on LUCENE-2019:

Here's a process-internal use-case (as I understand the meaning):
User hands me two tokens. I catenate and separate them with an internal-use char, then index.
Later, I get this term somehow from lucene, split on my internal-use char and hand back to
the user.
If lucene converts internal-use chars, this becomes impossible.

What's the use-case for handing lucene internal-use characters and not wanting it preserved?
 Couldn't you always use your internal-use characters, and then convert or remove them before
handing to lucene?

> 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