-
Notifications
You must be signed in to change notification settings - Fork 8.9k
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
HDDS-1191. Replace Ozone Rest client with S3 client in smoketests and docs #529
Conversation
… docs. Contributed by Elek, Marton.
to using the REST protocol instead of RPC. | ||
If no protocol is specified, the Ozone shell defaults to the native RPC | ||
protocol. | ||
1. Scheme - This should be `o3` which is the native RPC protocol to access |
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.
whitespace:end of line
Ozone ships with its own client library that supports both RPC (Remote | ||
Procedure Call) and REST (Representational State Transfer). This library is | ||
the primary user interface to ozone. | ||
Ozone ships with its own client library that supports RPC. For generic use cases the S3 |
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.
whitespace:end of line
Procedure Call) and REST (Representational State Transfer). This library is | ||
the primary user interface to ozone. | ||
Ozone ships with its own client library that supports RPC. For generic use cases the S3 | ||
compatible REST interface also can be used instead of the Ozone client. |
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.
whitespace:end of line
💔 -1 overall
This message was automatically generated. |
👍 I will commit this soon. |
Jira: SAMZA-1722: https://issues.apache.org/jira/browse/SAMZA-1722 Author: sanil15 <sanil.jain15@gmail.com> Reviewers: Prateek Maheshwari <pmaheshwari@apache.org> Closes apache#529 from Sanil15/SAMZA-1722
As it's discussed in the the parent jira the rest support for Ozone Client protocol can be removed to use S3 Rest API instead of that.
Some of the unit tests are already disabled, so it seems to be better to remove it from the documentation (and from the smoketests).
See: https://issues.apache.org/jira/browse/HDDS-1191