timsaucer commented on issue #754: URL: https://github.com/apache/datafusion-python/issues/754#issuecomment-2675805174
I think @Spaarsh is on the right track for this one, that it more likely needs to be resolved in the upstream repo. Or we would have to do some form of work around. In the file `datafusion/expr/src/udaf.rs` is where these column names are ultimately coming from it looks like. The column starts off as unqualified, but as the plan is built it gets the table projection and becomes qualified. Since there is no table specified the default is assigned. My thinking is that what we want to do is to update the logic upstream such that when we add in that qualifier we compare it to the default name. If they match, we wrap it in an alias without the qualifier. We could potentially do this under a feature flag depending on how people feel about it. -- As a side note, the above user request had a few things in it. This issue was just about the aliasing. The other topics - alias for read_parquet, using literals, etc - should not be included. Those are partially or fully complete anyways. -- 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
