[
https://issues.apache.org/jira/browse/HADOOP-2068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12548132
]
Billy Pearson commented on HADOOP-2068:
---------------------------------------
ok got a lot of work done on the php class to work with this interface
got insert,select,delete,scanner working by using socket connection (cut curl
out).
Still got some features to add to it like formating options where output is
going to be xml or other.
I guess when I am done I could make a new feature and upload a patch for the
php class if you guys let php be added to the project.
Any idea on when/if a way to get more then the latest version of max_versions
returned will be added?
say I have a max_versions = 3
How would I get the second oldest row?
I have no need for it on this project but could see where it would be handy on
others.
maybe a call like this
GET /[table_name]/row/[row_key]?columns=x:&versions=3
so far found row keys that have /'s in them do not get inserted return 500
error
and I found that row keys that have a ? in them get truncate at the ? so it
gets inserted but
Say row key = "aaa?bbb"
the row would get inserted as row key "aaa" only
> [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.
