-
Notifications
You must be signed in to change notification settings - Fork 2.9k
docs: replace minio with rustfs in quick start #14928
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
base: main
Are you sure you want to change the base?
Conversation
|
Hello @manuzhang @majinghe , After testing again, everything works perfectly. Thank you so much! We look forward to long-term, stable support for S3 storage. Screenshot
Command historyspark-defaults.confdocker-compose.yaml |
site/docs/spark-quickstart.md
Outdated
| - AWS_ACCESS_KEY_ID=rustfsadmin | ||
| - AWS_SECRET_ACCESS_KEY=rustfsadmin |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| - AWS_ACCESS_KEY_ID=rustfsadmin | |
| - AWS_SECRET_ACCESS_KEY=rustfsadmin | |
| - AWS_ACCESS_KEY_ID=admin | |
| - AWS_SECRET_ACCESS_KEY=password |
nit: can we keep this the same as before? i think its a good idea to do the smallest amount of change to the infra code. And if a change must be made, have it isolated to only the storage infra (minio/rustfs)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure, this is the default username and password for rustfs given by user, admin/password also works fine. Already changed those value.

As discussed in #14638, minio is under maintenance mode, so replacing the minio with RustFS. Testing works fine locally.
Testing steps:
Generating spark default conf
Running container
Running docker command to run all containers
Insert data
Data verification
Checking inserted data on RustFS instance