[
https://issues.apache.org/jira/browse/AVRO-3479?focusedWorklogId=757287&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-757287
]
ASF GitHub Bot logged work on AVRO-3479:
----------------------------------------
Author: ASF GitHub Bot
Created on: 15/Apr/22 04:10
Start Date: 15/Apr/22 04:10
Worklog Time Spent: 10m
Work Description: jklamer commented on PR #1631:
URL: https://github.com/apache/avro/pull/1631#issuecomment-1099832925
Call this officially ready! Except for the one outstanding issue: I can't
get the `cargo package` to recognize the avro_derive dependency that is local:
running it results in the error
```
Packaging apache-avro v0.14.0
Updating crates.io index
error: failed to prepare local package for uploading
Caused by:
no matching package named `avro_derive` found
location searched: registry `crates-io`
required by package `apache-avro v0.14.0`
```
Issue Time Tracking
-------------------
Worklog Id: (was: 757287)
Time Spent: 2h 40m (was: 2.5h)
> [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: 2h 40m
> 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)
