kellen opened a new pull request, #3543: URL: https://github.com/apache/avro/pull/3543
## What is the purpose of the change AVRO-4197 Fixes incorrect handling of `bytes` in the context of schema production introduced in #2529 (AVRO-3876). I am ambivalent about needing a special-case parameter `inSchemaContext` to revert back to the previous behavior. It seems like the basis for #2529 was that public json values (e.g. in metadata or via avro-tools) would more properly use the base64 encoding now provided rather than the previous `ISO_8859_1` encoding. Since `JacksonUtils` is used in both situations, some kind of use-case specific switch is unfortunately required. AVRO-3843 seems potentially related to this issue but I have not investigated. ## Verifying this change This change added tests and can be verified as follows: - Added `TestScheam.byteArrayDefaultField()` test verifying that the default `bytes` values can round-trip ## Documentation - Does this pull request introduce a new feature? no - If yes, how is the feature documented? not applicable -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
