[
https://issues.apache.org/jira/browse/AVRO-3814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17754449#comment-17754449
]
ASF subversion and git services commented on AVRO-3814:
-------------------------------------------------------
Commit 11249ae28333e9fc827f311b24bd9f9b4bb9e035 in avro's branch
refs/heads/avro-3814/schema-resolution-union from Rik Heijdens
[ https://gitbox.apache.org/repos/asf?p=avro.git;h=11249ae28 ]
AVRO-3814: Fix schema resolution for records in union types
The logic for validation records in Value::validate_internal() would be
too strict when resolving union types containing a record. This could
lead to a situation where schema resolution would fail because the
correct schema to use for a union type could not be identified.
This commit fixes this by passing a boolean `schema_resolution` to
`Value::validate_internal()` which governs whether schema_resolution
rules should be applied.
> [Rust] Schema resolution fails when extending a nested record with a union
> type
> -------------------------------------------------------------------------------
>
> Key: AVRO-3814
> URL: https://issues.apache.org/jira/browse/AVRO-3814
> Project: Apache Avro
> Issue Type: Bug
> Components: rust
> Reporter: Rik Heijdens
> Priority: Major
> Labels: pull-request-available
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> Consider the following schema:
> {noformat}
> {
> "type": "record",
> "name": "MyOuterRecord",
> "fields": [
> {
> "name": "inner_record",
> "type": [
> "null",
> {
> "type": "record",
> "name": "MyRecord",
> "fields": [
> {"name": "a", "type": "string"}
> ]
> }
> ],
> "default": null
> }
> ]
> }
> {noformat}
> Over time one might decide to add a new optional enum field 'b' to
> `MyRecord`, resulting in the following schema:
> {noformat}
> {
> "type": "record",
> "name": "MyOuterRecord",
> "fields": [
> {
> "name": "inner_record",
> "type": [
> "null",
> {
> "type": "record",
> "name": "MyRecord",
> "fields": [
> {"name": "a", "type": "string"},
> {
> "name": "b",
> "type": [
> "null",
> {
> "type": "enum",
> "name": "MyEnum",
> "symbols": ["A", "B", "C"],
> "default": "C"
> }
> ],
> "default": null
> }
> ]
> }
> ]
> }
> ],
> "default": null
> }
> {noformat}
> When one then serializes a message with the updated schema, and then attempts
> to deserialize it using the updated schema, while attempting to resolve it
> with the earlier schema, then schema resolution in Value::resolve_union()
> fails with `Error::FindUnionVariant`. This appears to be caused by
> `UnionSchema.find_schema_with_known_schemata()` failing to resolve the schema
> appropriately.
> I would not expect schema resolution to fail in this case. I will accompany
> this ticket with a test-case that allows reproduction.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
