[SPARK-36533][SS][FOLLOWUP] Address Trigger.AvailableNow in PySpark in SS guide doc#34597
Closed
HeartSaVioR wants to merge 1 commit into
Closed
[SPARK-36533][SS][FOLLOWUP] Address Trigger.AvailableNow in PySpark in SS guide doc#34597HeartSaVioR wants to merge 1 commit into
HeartSaVioR wants to merge 1 commit into
Conversation
HyukjinKwon
approved these changes
Nov 15, 2021
viirya
approved these changes
Nov 15, 2021
Contributor
Author
|
Thanks for the quick review (again)! Merging 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?
This PR addresses missing piece on adding Trigger.AvailableNow in Python code example in SS guide doc.
Why are the changes needed?
The SS guide doc doesn't mention a new trigger in Python code example.
Does this PR introduce any user-facing change?
Yes, doc change as above screenshot.
How was this patch tested?
N/A