-
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-738. Removing REST protocol support from OzoneClient #1329
Conversation
💔 -1 overall
This message was automatically generated. |
There are some minor issues, otherwise, it looks quite good.
|
import static org.apache.hadoop.ozone.s3.AWSAuthParser.AUTHORIZATION_HEADER; | ||
import static org.apache.hadoop.ozone.s3.AWSAuthParser.CONTENT_MD5; | ||
import static org.apache.hadoop.ozone.s3.AWSAuthParser.CONTENT_TYPE; | ||
import static org.apache.hadoop.ozone.s3.AWSAuthParser.HOST_HEADER; | ||
import static org.apache.hadoop.ozone.s3.AWSAuthParser.X_AMAZ_DATE; | ||
import static org.apache.hadoop.ozone.s3.AWSAuthParser.X_AMZ_CONTENT_SHA256; | ||
import org.junit.Test; | ||
import org.junit.runner.RunWith; | ||
import org.junit.runners.Parameterized; |
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
/retest |
💔 -1 overall
This message was automatically generated. |
@nandakumar131 @anuengineer Finally it's ready to commit. All the tests are fixed. There were two failures:
The biggest change in this patch is the following: Until now the |
💔 -1 overall
This message was automatically generated. |
I am going to commit this now. There some other changes we need to do in the future.
This patch is huge, so I expect various systems to fail, but this is the start of the 0.5.0 cycle, so we are fine and we can stabilize issues after this is committed if needed. |
Committed to the trunk. @elek Thank you for the contribution. @nandakumar131 Thanks for the review and discussion. |
Since we have functional {{S3Gateway}} for Ozone which works on REST protocol, having REST protocol support in OzoneClient feels redundant and it will take a lot of effort to maintain it up to date.
As S3Gateway is in a functional state now, I propose to remove REST protocol support from OzoneClient.
Once we remove REST support from OzoneClient, the following will be the interface to access Ozone cluster
See: https://issues.apache.org/jira/browse/HDDS-738