[AURON #1419]Add neverConvertReasonTag to record the reason for non-conversion.#1420
Merged
richox merged 1 commit intoapache:masterfrom Oct 9, 2025
Merged
Conversation
… non-conversion.
richox
approved these changes
Oct 9, 2025
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
…onversion.
Which issue does this PR close?
Closes #1419
Rationale for this change
During the Spark execution plan conversion process, add neverConvertReasonTag. After adding it, the Spark execution tree can be analyzed to determine which parts of the plan were not converted and the reasons for non-conversion.
What changes are included in this PR?
The following are the scenarios where conversion is currently not performed.
In these scenarios, after the convertStrategyTag is set to NeverConvert, the neverConvertReasonTag is added to describe why the plan was not converted.
Are there any user-facing changes?
How was this patch tested?
UT