alamb commented on issue #7063: URL: https://github.com/apache/arrow-rs/issues/7063#issuecomment-2786805463
> > replacing some parquet impls to operate on fields instead of types. > > I'm experimenting with this in DataFusion, too ( [apache/datafusion#15036](https://github.com/apache/datafusion/pull/15036) ) and there it's a fairly disruptive change (particularly for the UDFs). I know the version of `DataType::Extension(name, metadata)` was rejected but I wonder if `DataType::Extension(extension_type)` (never created without opt-in) would help minimize the surface area of supporting these types. (Although here there are probably sufficiently few internals that the change is not that difficult). I would personally be very open to the idea of adding a new enum to DataType. While it may not be strictly necessary from an API point of view, if it reduces churn and makes it easier to roll out extension types across the ecosystem it makes a lot of sense to me We could also potentially feature flag it for a while (`feature=extension`) as a way to roll it out before the next major release 🤔 -- 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: github-unsubscr...@arrow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
