[
https://issues.apache.org/jira/browse/HDFS-8527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Nauroth updated HDFS-8527:
--------------------------------
Attachment: HDFS-8527-HDFS-7240.001.patch
I'm attaching a patch that sets up the REST endpoints for Ozone in the
DataNode's HTTP server. The REST calls integrate with the back-end container
data pipeline handling. Right now, the back-end portion of this is stubbed,
just so that we can proceed with exercising the HTTP portion.
This took some effort to hoist a custom Jersey container into the Netty
pipeline so that we can take advantage of the JAX-RS annotations on the REST
service defintion. Long-term, after interfaces settle, I want to consider
removing this in favor of coding our own controller, similar to what the
existing DataNode HTTP endpoints do. Right now, it's very convenient to be
able to use the JAX-RS annotations while the interface evolves.
This is also the first time I've tried executing test-patch.sh on the Ozone
branch. I took the opportunity to clean up a few things even though some of
the changes aren't directly related to this patch.
[~anu], would you please review? Thank you!
> OzoneHandler: Integration of REST interface and container data pipeline
> back-end
> --------------------------------------------------------------------------------
>
> Key: HDFS-8527
> URL: https://issues.apache.org/jira/browse/HDFS-8527
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Reporter: Chris Nauroth
> Assignee: Chris Nauroth
> Attachments: HDFS-8527-HDFS-7240.001.patch
>
>
> This issue tracks development of OzoneHandler. This is a component within
> the DataNode that receives inbound requests parsed from the REST interface,
> dispatches to the underlying storage container data pipeline, and then
> returns an appropriate response to the REST layer for translation to an
> outbound HTTP response.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
