hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HBASE-1400) Improve REST interface semantics and efficiency
Date Sat, 30 May 2009 13:52:07 GMT

    [ https://issues.apache.org/jira/browse/HBASE-1400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12714717#action_12714717

stack commented on HBASE-1400:

Andrew: You've been busy.  This looks great.  How much does it differ from current REST (I've
not done a side-by-side but they seem close).  It looks like it might actually be up and working.
 Is that so?

Brian: What do you think?

How should we proceed?  REST has been refactored for 0.20.0.  This would be yet another implementation
it would seem.  What should we do?  Move our REST out of hbase and use stargate or use both
checking stargate into new contrib?  Or should stargate live elsewhere in its own project?

> 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.

View raw message