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
ERROR 0.31s | LogStructureFinderManagerTests.testFindCharsetGivenBinary <<< FAILURES!
> Throwable #1: java.lang.UnsupportedOperationException
> at __randomizedtesting.SeedInfo.seed([BB9C1AA2C3B090DF:4A943652575C61C1]:0)
> at sun.nio.cs.ext.ISO2022_CN.newEncoder(ISO2022_CN.java:76)
> at java.lang.StringCoding$StringEncoder.<init>(StringCoding.java:282)
> at java.lang.StringCoding$StringEncoder.<init>(StringCoding.java:273)
> at java.lang.StringCoding.encode(StringCoding.java:338)
> at java.lang.String.getBytes(String.java:918)
> at org.elasticsearch.xpack.ml.logstructurefinder.LogStructureFinderManager.findCharset(LogStructureFinderManager.java:166)
> at org.elasticsearch.xpack.ml.logstructurefinder.LogStructureFinderManagerTests.testFindCharsetGivenBinary(LogStructureFinderManagerTests.java:42)
> at java.lang.Thread.run(Thread.java:748)
The text was updated successfully, but these errors were encountered:
Some character sets cannot be encoded and this was tripping
up the binary data check in the ML log structure character
set finder.
The fix is to assume that if ICU4J identifies that some bytes
correspond to a character set that cannot be encoded and those
bytes contain zeroes then the data is binary rather than text.
Fixeselastic#33227
Some character sets cannot be encoded and this was tripping
up the binary data check in the ML log structure character
set finder.
The fix is to assume that if ICU4J identifies that some bytes
correspond to a character set that cannot be encoded and those
bytes contain zeroes then the data is binary rather than text.
Fixes#33227
Some character sets cannot be encoded and this was tripping
up the binary data check in the ML log structure character
set finder.
The fix is to assume that if ICU4J identifies that some bytes
correspond to a character set that cannot be encoded and those
bytes contain zeroes then the data is binary rather than text.
Fixes#33227
Build: https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+6.x+periodic/2636/console
I can reproduce locally on 6.x with:
Error:
The text was updated successfully, but these errors were encountered: