-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Unnest relation can't accept a field from its join table #13659
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comments
This should be a LATERAL JOIN, with the LATERAL keyword omitted. We do not support it yet. #10048 As stated in the PostgreSQL documentation.
|
Thanks for the information. Indeed, this is an implicit LATERAL join. I tried to use explicit LATERAL for it (I think they are equal 🤔 ) like
and get the error:
It seems that the physical plan isn't ready 🤔 I think there are two issues:
|
Hello! I'm happy to take on the logical planning piece of this. |
Update: moved to #10048 (comment) |
@goldmedal also pointed out this may be related to supporting table functions that take columns as arguments (DataFusion only support taking constants at the moment) |
After some more research, I think this ticket is now a dupe of #10048 |
Describe the bug
There is a common usage of SQL to operate the nested data that is allowed by Postgres and DuckDB but DataFusion can't execute.
Postgres
DuckDB
To Reproduce
It can be reproduced by the following SQL (I just added them in the sqlogicitests
unnest.slt
and ran the test)Then, it will throw the error:
Expected behavior
The test mentioned above should pass.
Additional context
No response
The text was updated successfully, but these errors were encountered: