hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bryan Duxbury (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-2068) [hbase] RESTful interface
Date Thu, 08 Nov 2007 20:55:50 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-2068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12541135
] 

Bryan Duxbury commented on HADOOP-2068:
---------------------------------------

Well, either Base64 encoding the data and sending it all together takes longer than requesting
each column individually, or it's the other way around. I'd be interested in seeing which
way it really is. 

I think it is perfectly acceptable to do the column-only approach in the short term and evaluate
the row oriented approach later.

> [hbase] RESTful interface
> -------------------------
>
>                 Key: HADOOP-2068
>                 URL: https://issues.apache.org/jira/browse/HADOOP-2068
>             Project: Hadoop
>          Issue Type: New Feature
>          Components: contrib/hbase
>            Reporter: stack
>            Priority: Minor
>
> A RESTful interface would be one means of making hbase accessible to clients that are
not java.  It might look something like the below:
> + An HTTP GET of  http://MASTER:PORT/ outputs the master's attributes: online meta regions,
list of tables, etc.: i.e. what you see now when you go to http://MASTER:PORT/master.jsp.
> + An HTTP GET of http://MASTER:PORT/TABLENAME: 200 if tables exists and HTableDescription
(mimetype: text/plain or text/xml) or 401 if no such table.  HTTP DELETE would drop the table.
 HTTP PUT would add one.
> + An HTTP GET of http://MASTER:PORT/TABLENAME/ROW: 200 if row exists and 401 if not.
> + An HTTP GET of http://MASTER:PORT/TABLENAME/ROW/COLUMNFAMILY: HColumnDescriptor (mimetype:
text/plain or text/xml) or 401 if no such table.
> + An HTTP GET of http://MASTER:PORT/TABLENAME/ROW/COLUMNNAME/: 200 and latest version
(mimetype: binary/octet-stream) or 401 if no such cell. HTTP DELETE would delete the cell.
 HTTP PUT would add a new version.
> + An HTTP GET of http://MASTER:PORT/TABLENAME/ROW/COLUMNNAME/TIMESTAMP: 200 (mimetype:
binary/octet-stream) or 401 if no such cell. HTTP DELETE would remove.  HTTP PUT would put
this record.
> + Browser originally goes against master but master then redirects to the hosting region
server to serve, update, delete, etc. the addressed cell

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message