duongcongtoai commented on PR #16016: URL: https://github.com/apache/datafusion/pull/16016#issuecomment-2907772662
> it seems like correlated subqueries with depth>1 does not reach optimizer as they report Schema Error: No field named xyz.col Actually this error is thrown after all optimizors are executed, the error is thrown because no existing optimizers are capable of handle nested subqueries. Now whether or not the depth is recorded in the optimizor or in the planning phase, we eventually have to convert the plan into DependentJoin, am i right? If in the future we have all the information we need, we can remove this "depth detection" logic inside this optimizor and go forward with whatever it provides (mainly decorrelation). -- 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
