-
Notifications
You must be signed in to change notification settings - Fork 5.3k
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
[native] Add native dynamic filter stats to operator stats for hbo #22734
Conversation
bd11e2d
to
7449fcd
Compare
I don't see documentation for me to review, perhaps I don't need to review this. Let me know if there's something I can help with! The description is empty, does this PR need a release note entry? |
a0287bf
to
4da1781
Compare
@steveburnett Hi, the pr description is updated. |
@ThriftStruct | ||
public class DynamicFilterStats | ||
{ | ||
private final Set<PlanNodeId> producerNodeIds; |
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.
These PlanNodeIds will be the PlanNodeId of the joins which has dynamic filter pushdown?
How do we know which nodes these filters are pushed down to?
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.
DynamicFilterStats is set in operator stats of those nodes that has dynamic filters.
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.
For example, if we have a query plan like:
join <- (probe side) project <- filter <- scan
where the dynamic filter pushdown is enabled, we should have project, filter and scan all in the producerNodeIds, right?
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.
Synced offline, the plan node ids will be the where the dynamic filter is from, which is the join node in the example I showed above.
ff95670
to
9be885d
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.
Thanks for the change!
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.
Thanks %minor
Exports the dynamic filter stats from native worker to coordinator: add DynamicFilterStats in OperatorStats and update presto protocol. Presto task collects the dynamic filter stats from velox.
Exports the dynamic filter stats from native worker to coordinator: