[
https://issues.apache.org/jira/browse/HADOOP-2068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12547969
]
Billy Pearson commented on HADOOP-2068:
---------------------------------------
After lots of work trying to get the php curl to work with the post option.
Looks like we will need support for content type "x-www-form-urlencoded". I
have tried many ways to get curl to encode the data and send as text/xml but
using the post fields option in php curl sends the data with content type
application/x-www-form-urlencoded. Sense that is not a supported content type I
get back a http error
406 Unsupported Accept Header Content: application/x-www-form-urlencoded
So is there a way we can add support for that?
If so we could still use the xml format as the data put make sure to urldecode
it first.
also can we have a set filed to post the xml to that the app knows about like
"xmldata" or something like that for post
So we can set the post field:
Example
xmldata='<?xml version="1.0" encoding="UTF-8"?> <column> <name>a: </name>
<value>YQ== </value> </column>';
Then the app knows where to look for the xml data.
> [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
> Assignee: Bryan Duxbury
> Priority: Minor
> Fix For: 0.16.0
>
> 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.
