[SPARK-47906][PYTHON][DOCS] Fix docstring and type hint of hll_union_agg#46128
Closed
zhengruifeng wants to merge 1 commit intoapache:masterfrom
Closed
[SPARK-47906][PYTHON][DOCS] Fix docstring and type hint of hll_union_agg#46128zhengruifeng wants to merge 1 commit intoapache:masterfrom
hll_union_agg#46128zhengruifeng wants to merge 1 commit intoapache:masterfrom
Conversation
zhengruifeng
commented
Apr 19, 2024
Contributor
Author
There was a problem hiding this comment.
function lit accepts both bool and Column
HyukjinKwon
approved these changes
Apr 19, 2024
9b5ef94 to
0ca3bff
Compare
Contributor
Author
|
thanks @HyukjinKwon merged to master |
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
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?
allowDifferentLgConfigK: Optional[bool]->Optional[Union[bool, Column]]Why are the changes needed?
fix incorrect docstring and type hints
Does this PR introduce any user-facing change?
yes, doc changes
How was this patch tested?
ci
Was this patch authored or co-authored using generative AI tooling?
no