fmcmac commented on issue #6543: URL: https://github.com/apache/datafusion/issues/6543#issuecomment-6245322422
Another data point for this issue, from a semantic layer that plans user SQL with DataFusion 53 and sends the unparsed SQL to other engines. Over 30 days, our planner logged 3,483 lines carrying 1 of the 3 duplicate-name messages: `Projections require unique expression names`, `Schema contains duplicate unqualified field name`, or `Schema contains qualified field name … which would be ambiguous`. They carry at most 373 distinct statement fingerprints. That is an upper bound: we sum fingerprints per message, so a statement that failed 2 ways counts twice. 3,356 of those lines, and at most 248 fingerprints, name `e.email`. The `e.email` shape we reproduced, `SELECT lower(e.email) AS email FROM employees e ORDER BY lower(e.email)`, fails on 53.0 and plans on 54.0. The `SELECT x, x` shape this issue names still fails on 55.0. `SELECT email, email FROM t` and `SELECT e.email, e.email AS email FROM t e` both hit `Projections require unique expression names`. Is #21260 still the plan of record? -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
