alamb commented on issue #13510:
URL: https://github.com/apache/datafusion/issues/13510#issuecomment-2626984284
Thank you for the investigation @rkrishn7 🙏
> Hello! I've dug into this issue a bit and it seems that the problem here
arises from the fact that the table name for each table scan in the plan
defaults to UNNAMED_TABLE ("?table?").
When I tested this reproducer last, when I disabled
`datafusion.execution.parquet.schema_force_view_types` (set it to false) then
the query would run
This suggests to me the problem wasn't related to ambiguous schemas but
instead somehow to some type coercion that was/wasn't happening 🤔
I would have thought this code was coerceing the join predicates already:
https://github.com/apache/datafusion/blob/d42b99474691a263c1dd53179e9ad1b481b1e819/datafusion/optimizer/src/analyzer/type_coercion.rs#L193-L192
But clearly something isn't working
--
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
