debugmiller commented on PR #8998: URL: https://github.com/apache/arrow-rs/pull/8998#issuecomment-3657173156
> Another alternative to rejiggering the dependencies, could be to allow users do provide their own decoders for certain fields. This is probably overkill for just variant, it would also make a nice API for other potential extension types (like some of the geospatial types from @kylebarron and @paleolimbot ) > > Similar to how [`with_encoder_factory`](https://docs.rs/arrow-json/57.1.0/arrow_json/writer/struct.EncoderOptions.html#method.with_encoder_factory) works for overriding writing of JSON fields, we could add a `with_decoder_factory` / `DecoderFactory` for customizing decoding and then provide a decoder factory implementation in `parquet-variant-compute` That seems like a nice compromise. I can look into pulling the tape decoder into `parquet-variant-compute` and adding an extension mechanism to the reader. Long(er) term I think its worth considering a more seamless integration for the canonical extension types. As a casual user it would be nice to not have to treat them any differently than standard types. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
