alamb commented on issue #12736: URL: https://github.com/apache/datafusion/issues/12736#issuecomment-3196110310
> [@alamb](https://github.com/alamb) -- I'm taking a look back at this ticket. There has been some changes, and I'm unclear as to long term plans. > > There is a new [FieldMetadata](https://github.com/apache/datafusion/blob/420a862faa98abdb941f22d6b7c9bd463a51c777/datafusion/expr/src/expr.rs#L448) which only applies to literals and unifies it's handling? What about non-literal fields? > > How (or is) this related to a consolidation of how schema field metadata is handled? Are we unifying a single wrapper abstraction to handle how merging (e.g. union), precedence (e.g. joins?), aggregates, lists, and/or casting is handled? TLDR is I don't know of any unified plan. What I would recommend doing is starting by documenting what (little) is known today (about projections and aliases) Then as we evolve and the plans become clearer, we will at least have a place to improve the documenetion I think starting with something even if it is incomplete, is better than the status quo (nothing) -- 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
