[AVRO-2789] Actually include non-spec metadata in the parsed Schema objects

• Type: New Feature
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Component/s: ruby
• Assignee: Unassigned
• Reporter: Chris Hoffman
• Created: 01/Apr/20 17:44
• Updated: 02/Apr/20 14:54

Description

Currently, the Avro specification is fine with fields having keys that aren't reserved by the specification. We use this freedom to give systems that consume Avro schemas hints about how they should construct ETL pipelines. The fact that gems built on top of the Avro gem can't access this non-specification metadata makes these tasks much harder.

I will be submitting a pull request to implement this, but I'm creating the ticket first so I can reference the ticket number in the branch name.

Issue Links

• links to: GitHub Pull Request #851