[jira] [Commented] (AVRO-3197) Rust: Disable logical type on failure

["ASF subversion and git services (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AVRO-3197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17469204#comment-17469204 ] 

ASF subversion and git services commented on AVRO-3197:
-------------------------------------------------------

Commit bce386623c79b204957f1c37c43079d1c51c2038 in avro's branch refs/heads/master from Martin Grigorov
[ https://gitbox.apache.org/repos/asf?p=avro.git;h=bce3866 ]

AVRO-3197 Fallback to the 'type' when the logical type does not support the type (#1340)

* AVRO-3197 Fallback to the 'type' when the logical type does not support the type

* AVRO-3197 Better formatting

* AVRO-3197 Allow only when the "type" is "string"

* AVRO-3197 Handle problematic complex type for date/time logical types

Read the complex type recursively. It seems Avro Java may produce {"type": {"type": "string", "avro.java.string": "String"}, "logicalType": "timestamp-millis"}}, i.e. logicalType is on the same level as the outer "type"

* AVRO-3197 Make Clippy happy

* AVRO-3197 Log a warning when a logical type is not supported by the Schema type

This is how Avro Java behaves.

> Rust: Disable logical type on failure
> -------------------------------------
>
>                 Key: AVRO-3197
>                 URL: https://issues.apache.org/jira/browse/AVRO-3197
>             Project: Apache Avro
>          Issue Type: Wish
>            Reporter: Guðjón
>            Assignee: Martin Tzvetanov Grigorov
>            Priority: Minor
>              Labels: pull-request-available
>         Attachments: weather.avro, weather2.avro
>
>          Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> I have a file containing avro records along with a schema. The schema contains a field that unfortunately has the type `String` but logical type `timestamp-millis`. The Java implementation of the avro spec doesn't complain and simply treats this field as a string, but the rust implementation will return an error since the string type doesn't match with the logical type of timestamp (long). 
> I wonder if there could be a possibility to optionally disregard the logical type if this failure is encountered.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)