[hotfix][docs] Fix FileSource monitor_continuously spelling - #28825
Open
fallintoplace wants to merge 1 commit into
Open
[hotfix][docs] Fix FileSource monitor_continuously spelling#28825fallintoplace wants to merge 1 commit into
fallintoplace wants to merge 1 commit into
Conversation
Generated-by: OpenAI API
Collaborator
spuru9
approved these changes
Jul 26, 2026
spuru9
left a comment
Contributor
There was a problem hiding this comment.
Make sense. Cross checked with the code.
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 is the purpose of the change
Four PyFlink examples call
monitor_continously, which does not exist. The correctFileSourceBuildermethod ismonitor_continuously. Users copying these examples receive anAttributeError.Brief change log
Verifying this change
The documentation builds successfully with Hugo. The incorrect spelling no longer occurs in the English or Chinese documentation.
Does this pull request potentially affect one of the following parts:
Documentation
Was generative AI tooling used to co-author this PR?