[SPARK-51401][SQL] Change ExplainUtils.generateFieldString to directly call QueryPlan.generateFieldString
#50169
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What changes were proposed in this pull request?
This pr change
ExplainUtils.generateFieldStringto directly callQueryPlan.generateFieldStringbecause these are identical methods.spark/sql/core/src/main/scala/org/apache/spark/sql/execution/ExplainUtils.scala
Lines 300 to 307 in 4b4bdcf
spark/sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/plans/QueryPlan.scala
Lines 789 to 795 in 4b4bdcf
Meanwhile, this is a TODO left by nemanjapetr-db in SPARK-50739.
Why are the changes needed?
Remove duplicated code.
Does this PR introduce any user-facing change?
No
How was this patch tested?
Pass Github Actions
Was this patch authored or co-authored using generative AI tooling?
No