You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Andrew Purtell (JIRA)" <ji...@apache.org> on 2009/05/30 20:54:07 UTC
[jira] Issue Comment Edited: (HBASE-1400) Improve REST interface
semantics and efficiency
[ https://issues.apache.org/jira/browse/HBASE-1400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12714752#action_12714752 ]
Andrew Purtell edited comment on HBASE-1400 at 5/30/09 11:53 AM:
-----------------------------------------------------------------
@Stack
Yes this works, in the sense that it will launch and all of the (manual) simple test cases enumerated in stargate-testing.pdf complete without error. I haven't checked to see what corner cases exist in Jersey or what capabilities I think Jetty gives for free e.g. transfer encoding of gzip or deflate.
Regarding integration with the project, it is my opinion that the REST bits should come out of core and Stargate should become a new contrib. I implemented this last week for some other project I am working on so it was built to a set of internal design criteria. For this version contributed to the community, I think the community should change it if the consensus on various details differs from what is in place now. While the iron is hot I would be willing to do some of that work. I like Jersey a lot. Building or changing complex behaviors takes little time. I built all of Stargate in less than one week, including learning curve.
was (Author: apurtell):
@Stack
Yes this works, in the sense that it will launch and all of the (manual) simple test cases enumerated in https://issues.apache.org/jira/secure/attachment/12409446/stargate-testing.pdf complete without error. I haven't checked to see what corner cases exist in Jersey or what capabilities I think Jetty gives for free e.g. transfer encoding of gzip or deflate.
Regarding integration with the project, it is my opinion that the REST bits should come out of core and Stargate should become a new contrib. I implemented this last week for some other project I am working on so it was built to a set of internal design criteria. For this version contributed to the community, I think the community should change it if the consensus on various details differs from what is in place now. While the iron is hot I would be willing to do some of that work. I like Jersey a lot. Building or changing complex behaviors takes little time. I built all of Stargate in less than one week, including learning curve.
> Improve REST interface semantics and efficiency
> -----------------------------------------------
>
> Key: HBASE-1400
> URL: https://issues.apache.org/jira/browse/HBASE-1400
> Project: Hadoop HBase
> Issue Type: Improvement
> Components: rest
> Reporter: Andrew Purtell
> Priority: Minor
> Attachments: stargate-0.0.1.zip, stargate-testing.pdf, stargate.pdf
>
>
> Improve the semantics of the REST interface: more metadata operations, bulk updates, protobufs (if Accept equals "application/x-protobuf" for GET or Content-Type equals the same for PUT or POST) instead of multipart/related (which is not supported now anyway) etc. for general efficiency and support for queries or scanners that return multiple KeyValues.
> I am working on a proposal.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.