goldmedal commented on PR #11724: URL: https://github.com/apache/datafusion/pull/11724#issuecomment-2267580253
> I rethink about what the issue we are solving, so I would like to make sure we have such issue in practice. Is there any valid query that shows the ambiguity between the identifier and column? > I guess it is not possible to project with the same name, thus the issue you mentioned probably not exist 🤔 ? Indeed, I think the final plan generated by the planner is fine. I tried many SQL cases, and none of them generated the issue I mentioned. I encountered this issue when I used LogicalPlanBuilder to build the plan directly while implementing some analyzer rules (e.g., the expand wildcard rule) to transform the plans. When I print the intermediate plan to debug or check something, I get confused about the columns if they aren't qualified. -- 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
