Spaarsh commented on issue #754: URL: https://github.com/apache/datafusion-python/issues/754#issuecomment-2676172533
@timsaucer I was thinking of going down the route of writing some workaround to this in our python interface since the issue originally mentioned it. Changing the logic upstream will take discussion. Should we implement a workaround here until then? Either way I suppose we need to open an issue for this in the ```datafusion``` repo. I am more towards making a workaround here first since people using python for working with data have a higher need for aliasing. They normally want to export the output in parquets (in this case) and/or refer to the output later down the pipeline. So this may significantly ease their woes. I am not sure of its impact on the upstream users. -- 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
