-
Notifications
You must be signed in to change notification settings - Fork 131
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug] orca: Inner Hashjoin failed with Partition selector #854
Comments
Step into this issue and found the root cause why the orca cannot generate a plan for it:
From the root group, we can see it uses inner hashjoin.
From the group 26 we can see that the 'partition selector' is added, but in the cost context 7,8 and 9 , no best expr is found. And in the 3 cost contexts , the
In group 21, motions are added. (group 21 is the child group of group 26) in function
the motion node will not propagate any partition info to its parent nodes. Then the when function Work around:
this can make the orca work for the above query. But better to resolve it without setting the GUC manually. If we can know there will be any motion node added below the inner hashjoin, we can do it. |
Apache Cloudberry version
No response
What happened
The original discussion about this issue is #807 (comment)
orca cannot generate a plan for it.
What you think should happen instead
No response
How to reproduce
run the sql above
Operating System
centos7
Anything else
No response
Are you willing to submit PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: