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 GitHub Bot (Jira)" <ji...@apache.org> on 2022/04/08 09:29:00 UTC

[jira] [Updated] (AVRO-3479) [rust] Derive Avro Schema macro

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

ASF GitHub Bot updated AVRO-3479:
---------------------------------
    Labels: pull-request-available  (was: )

> [rust] Derive Avro Schema macro
> -------------------------------
>
>                 Key: AVRO-3479
>                 URL: https://issues.apache.org/jira/browse/AVRO-3479
>             Project: Apache Avro
>          Issue Type: Improvement
>            Reporter: Jack Klamer
>            Assignee: Jack Klamer
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> The tracking Issue for the Avro Derive Feature of the rust SDK. 
> Proposal (copied from email):
> Have another rust crate that is importable as a feature on the main crate (in the same manner as serde derive), that will provide a derive proc_macro that implements a simple trait that returns the schema for the implementing type. Right now, schemas must be parsed from strings ( or read from files first), and closely coordinated with the associated struct. This makes sense for workflows that need to associate the same type across languages. For programs that are all within Rust, there are usability advantages of the proc_macro. 



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