findepi commented on issue #11513: URL: https://github.com/apache/datafusion/issues/11513#issuecomment-2370867867
> distinction between the types (this I think is clear when you look on how you can call [`LogicalPlan::schema`](https://docs.rs/datafusion/latest/datafusion/logical_expr/enum.LogicalPlan.html#method.schema)). Knowing this, some care needs to be taken in order to slowly introduce the distinction, which mainly comes in the form of storing the `DataType` alongside logical values. Well, if LogicalPlan is expressed in terms of logical types (what I'd like to be _the datafusion types_), then LogicalPlan::schema should return schema expressed in those types as well. Would be no need to track (arrow's) `DataType`. > The objective would be to eventually remove that knowledge and making it available directly through the data source (i.e. the RecordBatch) to support the run-time adaptiveness you are mentioning above and that've also mention in the proposal: Awesome. Let's graduate it from "proposal" to "project plan". -- 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...@datafusion.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: github-unsubscr...@datafusion.apache.org For additional commands, e-mail: github-h...@datafusion.apache.org
