You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the CompletionSuggester reserves 0x00 and 0xFF for internal use. We should throw an exception if those characters are used in an input string.
The text was updated successfully, but these errors were encountered:
The completion suggester reserves 0x00 and 0xFF as for internal use.
If those chars are used in the input string an IAE is thrown and the
input is rejected.
Closes#3648
I'm not up on exactly how UTF8 an UTF16 represent all the characters but I just wanted to make sure that if one of the bytes in one of the code points is 0x00 or 0xFF the suggester doesn't reject it.
see my comment - 0xFF is actually not valid and 0x00 can only be a single byte char so it will also be the 0 UTF-16 CP http://en.wikipedia.org/wiki/UTF-8
mute
pushed a commit
to mute/elasticsearch
that referenced
this issue
Jul 29, 2015
The completion suggester reserves 0x00 and 0xFF as for internal use.
If those chars are used in the input string an IAE is thrown and the
input is rejected.
Closeselastic#3648
Currently the CompletionSuggester reserves 0x00 and 0xFF for internal use. We should throw an exception if those characters are used in an input string.
The text was updated successfully, but these errors were encountered: