You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avro.apache.org by "Robert Yokota (Jira)" <ji...@apache.org> on 2022/08/22 03:01:00 UTC

[jira] [Work started] (AVRO-3274) Request for C# API to implement a JSON Encoder

     [ https://issues.apache.org/jira/browse/AVRO-3274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Work on AVRO-3274 started by Robert Yokota.
-------------------------------------------
> Request for C# API to implement a JSON Encoder
> ----------------------------------------------
>
>                 Key: AVRO-3274
>                 URL: https://issues.apache.org/jira/browse/AVRO-3274
>             Project: Apache Avro
>          Issue Type: Improvement
>          Components: csharp
>    Affects Versions: 1.10.2
>            Reporter: Andrew Benedek
>            Assignee: Robert Yokota
>            Priority: Major
>              Labels: pull-request-available
>
> This is a request or improvement.
> I have a .NET Core application that needs to publish AVRO JSON encoded messages to our Confluent Kafka REST API.  I can see that the Java and C++ API's have a JSON encoder, but I couldn't tell from the documentation whether the C# API has it, or at least it doesn't seem to.  The documentation for the C# API is a little light on for details.  The Kafka REST API supports JSON, and AVRO JSON, but not binary AVRO from what I understand.
> The main problem facing the plain JSON we are currently publishing is that when using an AVRO schema and the union type, we hit the problem described here https://issues.apache.org/jira/browse/AVRO-2899.  We need to generate the type information in the JSON in order to satisfy the validation in the Kafka REST API.  Hence, the need for an AVRO JSON encoder.
> I can't re-write the .NET application, so I'm faced with the prospect of using either the Java or C++ API's with some sort of wrappers or interoperability framework, which I'm desperately trying to avoid.
> Any assistance or suggestions would be much appreciated.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)