Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[SPARK-42896][SQL][PYTHON][FOLLOW-UP] Rename isBarrier to barrier, and correct docstring #40571

Closed
wants to merge 1 commit into from

Conversation

HyukjinKwon
Copy link
Member

What changes were proposed in this pull request?

This PR is a followup of proposes to fix:

  • Add versionchanged in its docstring.
  • Rename isBarrier to barrier to make it look Python friendly
  • Fix some wording and examples.

Why are the changes needed?

For better documentation, and make it more Python friendly.

Does this PR introduce any user-facing change?

Yes, it renames the parameter, and fixes the documentation.

How was this patch tested?

Linters in this PR should test them out.

@HyukjinKwon
Copy link
Member Author

cc @WeichenXu123 and @ueshin

@HyukjinKwon
Copy link
Member Author

Merged to master.

Copy link
Contributor

@WeichenXu123 WeichenXu123 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

HyukjinKwon pushed a commit that referenced this pull request Mar 29, 2023
### What changes were proposed in this pull request?

This is a follow-up of #40559 and #40571.

Renames `isBarrier` to `barrier` in Spark Connect, too.

### Why are the changes needed?

#40571 changed the argument name from `isBarrier` to `barrier`, so Spark Connect should follow it.

### Does this PR introduce _any_ user-facing change?

Yes, it renames the parameter.

### How was this patch tested?

Existing tests.

Closes #40579 from ueshin/issues/SPARK-42929/barrier.

Authored-by: Takuya UESHIN <ueshin@databricks.com>
Signed-off-by: Hyukjin Kwon <gurwls223@apache.org>
@HyukjinKwon HyukjinKwon deleted the SPARK-42896-followup branch January 15, 2024 00:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
4 participants