You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@avro.apache.org by GitBox <gi...@apache.org> on 2022/01/14 14:39:41 UTC

[GitHub] [avro] zolyfarkas commented on pull request #1217: AVRO-3135: ability to hook into schema ser/deser to implement schema refer…

zolyfarkas commented on pull request #1217:
URL: https://github.com/apache/avro/pull/1217#issuecomment-1013183705


   > The thing I like about current `.avsc` files is that they are complete. Using external references breaks that, and would require some form of compilation/resolution to name the schema complete again.
   > 
   > Instead, one can also use `.avdl` (IDL) files: these support resolving imports from both
   > 
   > * the file system (splitting large schemata in multiple files) and
   > * the class path (allowing your dependency system to import schemata by version)
   
   avsc and avdl are not equivalent, avsc is a data format for schemas while avdl is a format for interfaces/protocols.
   avdl is not serialization/deserialization friendly. but it's json representation .avpr is. 
   
   I understand your point.
   What about this change enabling a new schema format? let's call it ".ravsc".
   .avsc remains references free .ravsc introduces references support...
   
   Think about this PR about enabling the ability to implement .ravsc ....
   
   to understand why I think this is worthwhile, see the use cases I described [at](https://github.com/zolyfarkas/jaxrs-spf4j-demo/wiki/AvroReferences#why-avro-references).
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@avro.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org