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

ASF GitHub Bot logged work on AVRO-3434:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 09/Aug/22 07:44
            Start Date: 09/Aug/22 07:44
    Worklog Time Spent: 10m 
      Work Description: RyanSkraba commented on PR #1718:
URL: https://github.com/apache/avro/pull/1718#issuecomment-1209029889

   Oh my, yes thanks!  I'm sorry this didn't make this into the 1.11.1 release, 
I think I had it confused with another PR that was targeted for 1.12.0...  if 
we end up doing a 1.11.2 release, would this be a candidate?  We typically 
release every 6 months or so, and the major release happens in the last quarter.




Issue Time Tracking
-------------------

    Worklog Id:     (was: 799192)
    Time Spent: 3h 20m  (was: 3h 10m)

> .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
>             Fix For: 1.12.0
>
>          Time Spent: 3h 20m
>  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)

Reply via email to