[jira] Issue Comment Edited: (HADOOP-2068) [hbase] RESTful interface

["Billy Pearson (JIRA)" <ji...@apache.org>]

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

viper799 edited comment on HADOOP-2068 at 11/28/07 7:16 PM:
-----------------------------------------------------------------

how is this feature going to handle calling rows with /'s in the row keys?

example above
GET http://MASTER:PORT/TABLENAME/ROW/COLUMNNAME/:

my example call
GET http://192.168.1.200:60010/webdata/com.example.www/:http/source/

where "com.example.www/:http" is the row key and source is column 

the / in the row key will kill the request

      was (Author: viper799):
    how is this feature going to handle calling rows with /'s in the row keys?

example above
GET http://MASTER:PORT/TABLENAME/ROW/COLUMNNAME/:

my example call
GET http://192.168.1.200:60010/webdata/com.example.www/:http/source/

where "com.example.www/:http" is the row key

the / in the row key will kill the request
  
> [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
>         Attachments: rest-11-27-07-v2.patch, rest-11-27-07.3.patc, rest-11-27-07.patch, rest-11-28-07.2.patch, rest-11-28-07.3.patch, rest-11-28-07.patch, rest.patch
>
>
> 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.