[SPARK-31474][SQL][FOLLOWUP] Replace _FUNC_ placeholder with functionname in the note field of expression info#28314
Closed
yaooqinn wants to merge 1 commit intoapache:masterfrom
yaooqinn:SPARK-31474-F
Closed
[SPARK-31474][SQL][FOLLOWUP] Replace _FUNC_ placeholder with functionname in the note field of expression info#28314yaooqinn wants to merge 1 commit intoapache:masterfrom yaooqinn:SPARK-31474-F
yaooqinn wants to merge 1 commit intoapache:masterfrom
yaooqinn:SPARK-31474-F
Conversation
… name in the note field of expression info
|
Test build #121671 has started for PR 28314 at commit |
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.
What changes were proposed in this pull request?
FUNC is used in note() of
ExpressionDescriptionsince #28248, it can be more cases later, we should replace it with function name for documentationWhy are the changes needed?
doc fix
Does this PR introduce any user-facing change?
no
How was this patch tested?
pass Jenkins, and verify locally with Jekyll serve