hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brian Beggs (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HBASE-1400) Improve REST interface semantics and efficiency
Date Wed, 03 Jun 2009 21:28:07 GMT

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

Brian Beggs commented on HBASE-1400:


I was just going through the spec and I had wanted to ask about the formatting of the cell
or row query for multiple values.

The sample xml on the page is as follows:

  <Cell row="testrow" column="test:c1" timestamp="1128765413420141">

I was thinking it would be more efficient to do something like this:
  <row >
          Base64 Encoded Row Name
      <Cell column="test:c1" timestamp="1128765413420141">

This would probably be better as it would cut down on the size of the deliverable.  Could
maybe put the row name in as an attribute but I'm not sure how well that will work with a
base 64 encoded value.  Also the column name should come out base64 encoded as well.

What do you think?

> 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