[
https://issues.apache.org/jira/browse/AVRO-3448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17508584#comment-17508584
]
ASF subversion and git services commented on AVRO-3448:
-------------------------------------------------------
Commit 2bb7eb3a42b98f846936b4d9bc1e4345f6de6e5b in avro's branch
refs/heads/branch-1.11 from Jack Klamer
[ https://gitbox.apache.org/repos/asf?p=avro.git;h=2bb7eb3 ]
[AVRO-3448][rust] Rust name/namespace spec adherence work (#1602)
* resolved schema struct
* matrix testing started
* [AVRO-3448] encode, decode, parsing in allignment with name/namespace spec
* [AVRO-3448] clippy
* Update lang/rust/avro/src/util.rs
Co-authored-by: Martin Grigorov <[email protected]>
* Update lang/rust/avro/src/schema.rs
Co-authored-by: Martin Grigorov <[email protected]>
* [AVRO-3448] encode with Result return
* [AVRO-3448] clean up types and tests
* AVRO-3448: Fix a typo in an error variant
Signed-off-by: Martin Tzvetanov Grigorov <[email protected]>
Co-authored-by: Martin Grigorov <[email protected]>
Co-authored-by: Martin Tzvetanov Grigorov <[email protected]>
(cherry picked from commit 128510c4e9c3a714279aa7cea22eda19080521f7)
> Rust: Encoding Panic with valid schema and input
> -------------------------------------------------
>
> Key: AVRO-3448
> URL: https://issues.apache.org/jira/browse/AVRO-3448
> Project: Apache Avro
> Issue Type: Bug
> Reporter: Jack Klamer
> Assignee: Jack Klamer
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.11.1, 1.12.0
>
> Time Spent: 4h 40m
> Remaining Estimate: 0h
>
> After a recent bug regarding Rust Avro's schema ref was fixed to help
> preserve the parsing form of schema
> (https://issues.apache.org/jira/browse/AVRO-3433). This exposed an issue
> where named schemas defined with the rules of the spec (depth first, left to
> right), are not available to the encoding workflow because it indexes schemas
> as it traverses the data. This is a problem for the common use case of
> defining a record within an optional field and it being encoded as Null, and
> not having that type then available during encoding for the next field.
>
> This was patched for level + 1 schema definitions but was not solved within
> the fullness of the spec
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
