[
https://issues.apache.org/jira/browse/AVRO-3468?focusedWorklogId=762803&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-762803
]
ASF GitHub Bot logged work on AVRO-3468:
----------------------------------------
Author: ASF GitHub Bot
Created on: 27/Apr/22 11:08
Start Date: 27/Apr/22 11:08
Worklog Time Spent: 10m
Work Description: anekdoti commented on PR #1622:
URL: https://github.com/apache/avro/pull/1622#issuecomment-1110871948
You are right, I was mistaken about the specification and remembered it
wrongly. But I am still wondering why ISO-8859-1 is used for the JSON encoding
of fixed and bytes (I don't mean the binary encoding, just the JSON
representation). The JSON RFC
(https://datatracker.ietf.org/doc/html/rfc8259#section-8.1) says that all text
that crosses the boundaries of a closed ecosystem must be encoded with UTF-8.
In my particular case, the choice of the encoding for example prevents me from
a straightforward integration with Snowflake (which assumes UTF-8 encoding).
But I guess this is something that can hardly be changed for backwards
compatibility reasons...
Issue Time Tracking
-------------------
Worklog Id: (was: 762803)
Time Spent: 7.5h (was: 7h 20m)
> Default values for logical types not supported
> ----------------------------------------------
>
> Key: AVRO-3468
> URL: https://issues.apache.org/jira/browse/AVRO-3468
> Project: Apache Avro
> Issue Type: Bug
> Components: csharp
> Affects Versions: 1.11.0
> Reporter: Lucas Heimberg
> Assignee: Martin Tzvetanov Grigorov
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.11.1, 1.12.0
>
> Time Spent: 7.5h
> Remaining Estimate: 0h
>
> The C# implementation of Avro does not support default values for logical
> types on deserialization. It seems that the method EncodeDefaultValue in
> Avro.IO.Resolver is lacking a case for logical types that resorts to the base
> schema.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
