elek commented on pull request #1270:
URL: https://github.com/apache/hadoop-ozone/pull/1270#issuecomment-667714388
> Let's say when s3G started all buckets are created under volume s3v.
>
> Now different S3G's started using different volumes, now when the user
wants to use the bucket in o3fs, now he is not sure which volume to use.
I might have a different view this, because I think here are multiple,
different roles, which are mixed here.
* The **administrators** can modify the volume mounting.
* **Users** will use s3g
I think it's acceptable, if the administrator modifies some fundamental part
of the environment setup, the user should be notified. It's very similar to a
DNS name refactor. There are cases where the knowledge of the users should be
updated.
I think it's acceptable, and this is the responsibility of the administrator
to judge if it's ok or not in a specific environment / company culture.
There are also cases when the administrator would like to start with `/home`
instead of `s3v` volume names from the day 1. The volume name won't be changed
anymore, but in this setup, a different
> And also one more point, using a single volume for S3G buckets came to
eliminate a command which was there before ozone s3 path, ... now with this
feature, we will be back to the same issue.
Similar, but not the same. There are significant differences:
1. volume names are not cryptic anymore
2. **all** buckets use the same volume name (don't need to check for every
bucket, enough to remember to the configuration)
> Okay coming back to the comment, to get this in are you proposing we need
to remove the warning which we have added in the code?
Actually it was suggested by @arp7, but yes. I am fine with that. I think we
shold keep it in `ozone-default.xml`, too. We can assume that if somebody
checks the `ozone-default.xml`, they are power users or developers.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
