-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Add FilterProjectReplayer #11351
Add FilterProjectReplayer #11351
Conversation
✅ Deploy Preview for meta-velox canceled.
|
bbcfc21
to
03c8edf
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@duanmeng LGTM % minors. Could you add a test for project in velox/exec/OperatorTraceTest.cpp? Thanks!
VELOX_CHECK( | ||
!isFilterProject(filterNode), | ||
"If the target node is aFilterNode, it must be a standalone " | ||
"FilterNode, without a ProjectNode as its parent."); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
without a ProjectNode as its consumer ?
not sure if it should call parent or consumer. It is basically the downstream node of filter node? thanks!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just use "If the target node is a FilterNode, it must be a standalone FilterNode"?
c577fa0
to
91ae9d8
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@duanmeng LGTM. Thanks for the update!
@xiaoxmeng has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator. |
@xiaoxmeng merged this pull request in ad27145. |
Conbench analyzed the 1 benchmark run on commit There were no benchmark performance regressions. 🎉 The full Conbench report has more details. |
Add FilterProjectReplayer. For the plan fragment involving
FilterNode->ProjectNode, users should use the ProjectNode
ID for tracing. This is because the planner will combine these
two operators into a single FilterProject operator. During replay,
the ProjectNode ID will locate the trace data directory.
Part of #9668