[ https://issues.apache.org/jira/browse/AVRO-3434?focusedWorklogId=799184&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-799184 ]
ASF GitHub Bot logged work on AVRO-3434: ---------------------------------------- Author: ASF GitHub Bot Created on: 09/Aug/22 07:17 Start Date: 09/Aug/22 07:17 Worklog Time Spent: 10m Work Description: martin-g merged PR #1718: URL: https://github.com/apache/avro/pull/1718 Issue Time Tracking ------------------- Worklog Id: (was: 799184) Time Spent: 3h (was: 2h 50m) > .NET/#C: Support LogicalSchema for ReflectReader/Writer > ------------------------------------------------------- > > Key: AVRO-3434 > URL: https://issues.apache.org/jira/browse/AVRO-3434 > Project: Apache Avro > Issue Type: Improvement > Components: csharp > Reporter: Khrystyna Popadyuk > Assignee: Khrystyna Popadyuk > Priority: Blocker > Labels: pull-request-available > Time Spent: 3h > Remaining Estimate: 0h > > Hi, > I am working on a .NET/C# project that uses Kafka with Avro > serialization/deserialization in an event streaming platform. > .NET Apache.Avro nuget package contains two different set of classes for > serialization/deserialization: - SpecificReader, SpecificWriter - > ReflectReader, ReflectWriter. We have chosen ReflectReader/Writer > ([https://avro.apache.org/docs/current/api/csharp/html/md_src_apache_main_Reflect_README.html]) > so we can use POCO classes to represent a message. > I noticed that ReflectReader/Writer does not support LogicalSchema. There are > default converters and Avro field attribute instead (they are extendable and > flexible). > My questions are: > * is it intentional to not support LogicalSchema for ReflectReader/Writer? > * does it mean that we should not mix services that use LogicalSchema (third > party or just written on Java, Python or other languages) with ones that use > ReflectReader/Writer? > > Thanks, > Khrystyna -- This message was sent by Atlassian Jira (v8.20.10#820010)