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

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

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

AVRO-3216 Reuse records' schema by name (#1345)

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

Signed-off-by: Martin Tzvetanov Grigorov <[email protected]>

* 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"

Signed-off-by: Martin Tzvetanov Grigorov <[email protected]>

* AVRO-3216 Allow to reuse record's schema by name

* AVRO-3216 Extend the test case to do more assertions

* AVRO-3216 Print err with Debug

> 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
>             Fix For: 1.12.0
>
>         Attachments: weather.avro, weather2.avro
>
>          Time Spent: 1h 20m
>  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)

Reply via email to