Fix EMR operator parameter documentation and naming #53446
Merged
Conversation
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
- Correct parameter names (waiter_check_interval_seconds -> waiter_delay) - Improve English grammar and wording in docstrings - Standardize parameter documentation format - Fix default value descriptions to match actual code Signed-off-by: BobDu <i@bobdu.cc>
boring-cyborg
bot
added
area:providers
provider:amazon
dominikhei
reviewed
Jul 17, 2025
…epsOperator Signed-off-by: BobDu <i@bobdu.cc>
prdai
approved these changes
Jul 17, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.
Fix wait_for_completion parameter documentation - Remove references to deleted parameters in docstring
Fix example file parameter references - Correct usage of removed parameters in example code
Minor parameter documentation improvements - Enhance default value descriptions for consistency
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rstor{issue_number}.significant.rst, in airflow-core/newsfragments.