Changed extractExecutedPlan to consider ResultQueryStageExec for Databricks 13.3 [databricks]
#9690
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
build |
Signed-off-by: Raza Jafri <[email protected]>
razajafri
changed the title
extractExecutedPlan to consider ResultQueryStageExec [databricks]extractExecutedPlan to consider ResultQueryStageExec for Databricks 13.3 [databricks]
|
CI failed with |
|
build |
1 similar comment
|
build |
jlowe
approved these changes
Nov 14, 2023
sameerz
added
the
task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR handles an issue where when AdaptiveQueryEngine is turned a ResultQueryStageExec is returned which we need to look into to determine if it contains the plan we expect to be on the CPU.
fixes #9490