You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avro.apache.org by "Khrystyna Popadyuk (Jira)" <ji...@apache.org> on 2022/03/07 03:48:00 UTC
[jira] [Created] (AVRO-3434) .NET/#C: Support LogicalSchema for ReflectReader/Writer
Khrystyna Popadyuk created AVRO-3434:
----------------------------------------
Summary: .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
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, Phyton or other languages) with ones that use ReflectReader/Writer?
Thanks,
Khrystyna
--
This message was sent by Atlassian Jira
(v8.20.1#820001)