Is your feature request related to a problem or challenge? Please describe what you are trying to do.
Improve the boundary between the arrow-avro codec and decoder by ensuring planning logic related to the skipper is handled in codec.rs and not during decoder construction or parsing.
Describe the solution you'd like
I'd recommend pushing the writer-wire planning fully into codec.rs, instead of carrying full AvroDataTypes down into record.rs and having Skipper::from_avro reconstruct the skip tree there. However this can always be done in a follow-up as well.
Originally posted by @jecsand838 in #9605 (comment)
Describe alternatives you've considered
- Leaving the code structure as is, which is fine for now, but overtime will likely reduce maintainability.
Additional context
N/A
Is your feature request related to a problem or challenge? Please describe what you are trying to do.
Improve the boundary between the
arrow-avrocodec and decoder by ensuring planning logic related to the skipper is handled incodec.rsand not during decoder construction or parsing.Describe the solution you'd like
I'd recommend pushing the writer-wire planning fully into
codec.rs, instead of carrying fullAvroDataTypes down intorecord.rsand havingSkipper::from_avroreconstruct the skip tree there. However this can always be done in a follow-up as well.Originally posted by @jecsand838 in #9605 (comment)
Describe alternatives you've considered
Additional context
N/A