You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avro.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2022/08/09 07:18:00 UTC

[jira] [Commented] (AVRO-3434) .NET/#C: Support LogicalSchema for ReflectReader/Writer

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

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

Commit 7fd454e4a0880e928d7fbc417895a4ab4e4ad3cf in avro's branch refs/heads/master from KhrystynaPopadyuk
[ https://gitbox.apache.org/repos/asf?p=avro.git;h=7fd454e4a ]

AVRO-3434: support logical schemas in reflect reader and writer (#1718)

* avro-3434 support logical schemas in reflect reader and writer

* avro-3434 add apache licence to files

* avro-3434 update unit tests

> .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)