[
https://issues.apache.org/jira/browse/LUCENE-2019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12772118#action_12772118
]
Steven Rowe commented on LUCENE-2019:
-------------------------------------
Lucene indexes can be used both process-internally and across processes (e.g.
Solr).
This patch enforces the Lucene-index-as-process-external view, and excludes the
possiblity that a Lucene index is used process-internally.
Since Lucene itself uses U+FFFF internally, no clients can use it for their own
purposes. This patch rationalizes handling of internal-use-only characters,
such that Lucene's behavior is made consistent for all of them.
Instituting this consistency precludes Lucene-index-as-process-internal use
cases. I would argue that the price of consistency is in this case too high.
My vote: document the crap out of the U+FFFF Lucene-internal-use character and
drop this patch.
If people want to use internal-use-only characters in Lucene indexes, as long
as Lucene doesn't reserve them for its own use, why stop them?
> 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]
