[
https://issues.apache.org/jira/browse/LUCENE-2019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12772246#action_12772246
]
Earwin Burrfoot commented on LUCENE-2019:
-----------------------------------------
bq. if you disagree with this patch, then you should also disagree with
treating U+FFFF special! I don't see how in the world U+FFFF is different than
any other codepoint in the noncharacter category in this regard!
Yes! The best treatment a library can offer to your data if you're not
explicitly requesting transformation is transparently passing it in and out.
If Lucene had cleanly separated text/binary data API, it would be okay to
mangle text input. But now such mangling just messes up other people's attempts
of building said type-safe API on top of Lucene.
> map unicode process-internal codepoints to replacement character
> ----------------------------------------------------------------
>
> Key: LUCENE-2019
> URL: https://issues.apache.org/jira/browse/LUCENE-2019
> 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 process-internally.
> 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: [email protected]
For additional commands, e-mail: [email protected]
