Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
1.8.0
-
None
-
None
Description
A Kudu user reported ksck output that could not be deserialized as valid UTF-8. We should escape output like this so that it's always parseable.
We should also look at other places where we have JSON input/output and make sure we always produce valid UTF-8.
Note that there may be backwards incompatibilities to consider. From Todd:
Fixing this is a little bit incompatible, but for something like partition
keys I think we probably should do it anyway and release note it,
considering partition keys are quite likely to be invalid UTF8.