add UnicodeUtil.nextValidUTF16String
-------------------------------------
Key: LUCENE-2121
URL: https://issues.apache.org/jira/browse/LUCENE-2121
Project: Lucene - Java
Issue Type: Task
Reporter: Robert Muir
Fix For: Flex Branch
In flex branch, TermRef must not contain unpaired surrogates, etc.
But in trunk/previous releases, people could (and do) seek to these.
Also some lucene multitermqueries will generate these invalid seek locations,
even now (which we should separately fix)
I think the common case is already handled with a hack in
SegmentReader.LegacyTermEnum, but we should clean up this hack and handle all
cases.
I would also like to use this nextValidUTF16String in LUCENE-1606, and there
might be other places it could be used for better bw compat.
--
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: java-dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-dev-h...@lucene.apache.org
