[HDDS-5828] [HTTPFSGW] Add proper handling for unsupported operations

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.4.0
• Labels: pull-request-available
• Assignee: Zita Dombi
• Reporter: István Fajth
• Created: 06/Oct/21 08:33
• Updated: 14/Dec/23 15:05
• Resolved: 28/Nov/21 21:36

Description

As stated in the design doc, we need to address unsupported calls properly in HTTPFS GW. There is a default error handler, that handles queries that are supported by the HDFS NameNode but are not supported by the HDFS HTTPFSGW implementation, we can partly rely on that, but there are some operations that would require extra care.

Relevant part of the design:
Handling of unsupported calls
For calls that we do not have support for in Ozone, HTTP 501 Not Implemented status code has to be returned. As described in RFC2616 by the World Wide Web Consortium, this status code is the response to be given when "The server does not support the functionality required to fulfill the request. This is the appropriate response when the server does not recognize the request method and is not capable of supporting it for any resource."
Handling of invalid operations on volumes or buckets
For example file creation is not allowed by the ofs scheme on volume and bucket paths, these operations should return an HTTP 400 Bad Request status code, with a proper error message in the response body.

Issue Links

• links to: GitHub Pull Request #2862