[
https://issues.apache.org/jira/browse/AVRO-3448?focusedWorklogId=741230&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-741230
]
ASF GitHub Bot logged work on AVRO-3448:
----------------------------------------
Author: ASF GitHub Bot
Created on: 14/Mar/22 20:45
Start Date: 14/Mar/22 20:45
Worklog Time Spent: 10m
Work Description: martin-g commented on pull request #1602:
URL: https://github.com/apache/avro/pull/1602#issuecomment-1067269473
@travisbrown You might want to review this PR too.
--
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: issues-unsubscr...@avro.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 741230)
Time Spent: 40m (was: 0.5h)
> 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
> Time Spent: 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)
