bharatviswa504 commented on pull request #1270:
URL: https://github.com/apache/hadoop-ozone/pull/1270#issuecomment-667561738
>As I wrote in my previous comment, bucket link is not a replacement of this
configuration. This configuration can expose > >an other volume and all buckets.
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. As said in
the PR description this can cause this kind of issue. I understood the use
case of you, have mentioned, and also we are not totally eliminating this, if
someone is advanced user and knows what he is doing, they can still use this,
but they will see the warning. (But it is not documented, I think this can be
addressed with a new page with your proposal)
And also one more point, using a single volume for S3G buckets came to
eliminate a command which was there before `ozone s3 path`, thinking that is an
extra burden and now the user needs to know the volume name from this command.
(And also volume names are cryptic) now with this feature, we will be back to
the same issue.
So, to avoid this, might be admin need to give one S3G URL and the volume
used underneath it to users. (And admin can go ahead and create the volumes and
provide appropriate permissions)
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?
```
LOG.warn(OZONE_S3_VOLUME_NAME + " is deprecated. Consider using bucket
" +
"link command to access volume/buckets created via ozone shell " +
"through S3Gateway and also to access buckets created by S3Gateway
" +
"version less than or equal to 0.5.0");
```
----------------------------------------------------------------
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]
