-
Notifications
You must be signed in to change notification settings - Fork 439
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
[GLUTEN-8010][CORE] Don't generate native metrics if transformer don't generate relNode #8011
Changes from 5 commits
2336fb4
416ca53
9bafdd8
78f2c93
0ddc7b3
9e4b75f
3affe1c
a0d15f1
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -54,9 +54,6 @@ object MetricsUtil extends Logging { | |
MetricsUpdaterTree( | ||
smj.metricsUpdater(), | ||
Seq(treeifyMetricsUpdaters(smj.bufferedPlan), treeifyMetricsUpdaters(smj.streamedPlan))) | ||
case t: TransformSupport if t.metricsUpdater() == MetricsUpdater.None => | ||
assert(t.children.size == 1, "MetricsUpdater.None can only be used on unary operator") | ||
treeifyMetricsUpdaters(t.children.head) | ||
case t: TransformSupport => | ||
MetricsUpdaterTree(t.metricsUpdater(), t.children.map(treeifyMetricsUpdaters)) | ||
case _ => | ||
|
@@ -219,6 +216,7 @@ object MetricsUtil extends Logging { | |
}) | ||
|
||
mutNode.updater match { | ||
case MetricsUpdater.None => | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Are we sure about this? The code is likely something done by Did you check the UI? Are all the metrics still normal with this change? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I see. My impressions about this part of code is:
Would you like to check whether the two rule apply? And if we no longer need |
||
case ju: HashJoinMetricsUpdater => | ||
// JoinRel outputs two suites of metrics respectively for hash build and hash probe. | ||
// Therefore, fetch one more suite of metrics here. | ||
|
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.
It will cause operatorId inconsistencies. It should be handled in
updateTransformerMetricsInternal
. cc @zhztheplayer