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

[DOC] Getting started guide for UCX shuffle #272

Closed
abellina opened this issue Jun 23, 2020 · 1 comment · Fixed by #390
Closed

[DOC] Getting started guide for UCX shuffle #272

abellina opened this issue Jun 23, 2020 · 1 comment · Fixed by #390
Assignees
Labels
documentation Improvements or additions to documentation shuffle things that impact the shuffle plugin

Comments

@abellina
Copy link
Collaborator

Currently there is no documentation on how to get started with the UCX shuffle. There should be a Getting Started guide and documentation on capabilities and issues.

@abellina abellina added ? - Needs Triage Need team to review and classify documentation Improvements or additions to documentation shuffle things that impact the shuffle plugin labels Jun 23, 2020
@sameerz sameerz removed the ? - Needs Triage Need team to review and classify label Jun 29, 2020
@abellina abellina self-assigned this Jul 15, 2020
@abellina
Copy link
Collaborator Author

Now that UCX has binaries for v1.8.1, I'll incorporate into my instructions and publish a PR.

https://github.com/openucx/ucx/releases/tag/v1.8.1

@sameerz sameerz linked a pull request Jul 18, 2020 that will close this issue
pxLi pushed a commit to pxLi/spark-rapids that referenced this issue May 12, 2022
tgravescs pushed a commit to tgravescs/spark-rapids that referenced this issue Nov 30, 2023
Signed-off-by: spark-rapids automation <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation shuffle things that impact the shuffle plugin
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants