[jira] [Commented] (AVRO-3135) Add schema serialization/deserialization hooks, to aid implementation of "schema references"

["Oscar Westra van Holthe - Kind (Jira)" <ji...@apache.org>]

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

Oscar Westra van Holthe - Kind commented on AVRO-3135:
------------------------------------------------------

On a more opinionated note (so please don't read too much in it), when reading the rationale ([why-avro-references|https://github.com/zolyfarkas/jaxrs-spf4j-demo/wiki/AvroReferences#why-avro-references]) I see avro schemas used as header in a REST call to tell a server what to expect.

This is quite a bit of overhead: for anything that's not a large list, it rather negates the need for a compact format like Avro. JSON would be a better fit instead.

Also, the binary message encoding already includes a schema fingerprint. So one could also include a header with a schema registry URL maybe even with a marker to fill in the fingerprint to retrieve -- this is a lot smaller than a schema).

> Add schema serialization/deserialization hooks, to aid implementation of "schema references"
> --------------------------------------------------------------------------------------------
>
>                 Key: AVRO-3135
>                 URL: https://issues.apache.org/jira/browse/AVRO-3135
>             Project: Apache Avro
>          Issue Type: New Feature
>          Components: java
>            Reporter: Zoltan Farkas
>            Assignee: Zoltan Farkas
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> This capability's main use case is to allow easy implementation of schema references. For a more detailed writeup please see: https://github.com/zolyfarkas/jaxrs-spf4j-demo/wiki/AvroReferences#why-avro-references



--
This message was sent by Atlassian Jira
(v8.20.1#820001)