You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please check the FAQ documentation before raising an issue
Describe the bug (required)
When we profile the query whose execution plan has join related plan node, we get the wrong dependencies in join plan node description, such as following table, the third column should have two dependencies, but now there is the only one.
Please check the FAQ documentation before raising an issue
Describe the bug (required)
When we profile the query whose execution plan has join related plan node, we get the wrong dependencies in join plan node description, such as following table, the third column should have two dependencies, but now there is the only one.
The
Join
plan node inheriting theSingleDependencyNode
result in the incorrect result.Your Environments (required)
uname -a
g++ --version
orclang++ --version
lscpu
a3ffc7d8
)How To Reproduce(required)
Steps to reproduce the behavior:
Expected behavior
Additional context
The text was updated successfully, but these errors were encountered: