It won't generate runtime errors for invalid UTF-8, but instead replaces erroneous sequences with the character "�":
I think can be considered a compatible change, since it won't break existing applications. Today attempts to switch a field from bytes to string would fail. I suppose an application could currently rely on such failures, but I consider that unlikely enough that I'm willing to ignore it. Do others disagree?
- revert this change entirely, declaring it incompatible
- revert just the change to the specification, so that Avro Java is more lenient in what conversions it permits than the specification (following Postel's law)
- file issues to update the
AVRO-1315 schema validation to permit such conversions
- also file issues for C, C++ and C# to update their schema resolution to support these conversions