[
https://issues.apache.org/jira/browse/AVRO-2429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16959901#comment-16959901
]
Michael A. Smith commented on AVRO-2429:
----------------------------------------
This is related to AVRO-2580. In that ticket I discovered that the logical and
literal types are not forced to match, and that this isn't covered due to a
flaw in the tests (the assertion error is caught by too-wide error handling,
also see AVRO-2577). Let me get the fixes for AVRO-2580 merged in, which will
fix the tests, and then we can make progress on this with valid tests in place.
> Avro 1.9.0 fails when reading logical types other than "decimal"
> ----------------------------------------------------------------
>
> Key: AVRO-2429
> URL: https://issues.apache.org/jira/browse/AVRO-2429
> Project: Apache Avro
> Issue Type: Bug
> Components: python
> Affects Versions: 1.9.0
> Reporter: Chamikara Madhusanka Jayalath
> Assignee: Ryan Skraba
> Priority: Major
> Attachments: uuid.avro
>
>
> [https://github.com/apache/avro/pull/82] added support for Avro "decimal"
> logical type but also added an assertion that results in a reader failing for
> other logical types.
> [https://github.com/apache/avro/blob/master/lang/py/src/avro/schema.py#L821]
> I believe this is a regression since previously avro library used to read the
> underlying primitive type instead of failing.
> Can we revert the behavior for logical types that are not "decimal" by
> removing this assertion and reverting to the old (avro 1.8.1) behavior of
> returning the primitive type ?
>
> cc: [~Fokko] [~mtth]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)