hbase-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrew Purtell <apurt...@apache.org>
Subject Re: Queries regarding REST API
Date Tue, 01 Feb 2011 20:20:31 GMT
> The problem is how do you represent what could be binary
> data [...]

Exactly. Base64 it required if you are using XML representation (text/xml) because the basic
data type in HBase is byte[]. 

You also have the option of binary representations, either protobuf (application/x-protobuf)
or raw value (application/octet-stream). In those cases the data is sent in binary form. 

Using protobufs requires your client do the necessary unmarshalling of course.

Using raw (application/octet-stream) currently has limitations. See https://issues.apache.org/jira/browse/HBASE-1788.
It's not possible to query more than one version of a value at a time or return more than
one value out of a scanner at a time or insert more than one value at a time. Adding multipart
support would solve that problem. 

Best regards,

    - Andy

Problems worthy of attack prove their worth by hitting back.
  - Piet Hein (via Tom White)

--- On Tue, 2/1/11, Stack <stack@duboce.net> wrote:

> From: Stack <stack@duboce.net>
> Subject: Re: Queries regarding REST API
> To: user@hbase.apache.org
> Date: Tuesday, February 1, 2011, 11:21 AM
> On Tue, Feb 1, 2011 at 10:57 AM, Hari
> Sreekumar
> <hsreekumar@clickable.com>
> wrote:
> > Hi,
> >
> > I am planning to implement the REST API to query my
> > HBase tables in production. The documentation mentions that the
> > stargate api is not production ready.
> Sorry.  Where did you see that.  We need to fix
> that.  I believe at least the yfrog folks are using REST in
> production (Correct me if I'm wrong Jack).
> > Secondly, I am getting base64 encoded values when I use REST.
> > Is there any other encoding possible? Decoding base64 on client
> > side will be a big effort> for me. Is there a way I can get it
> > in a non-encoded way?
> >
> I'lll let those that know the REST gateway better than I
> answer this question.  The problem is how do you represent what
> could be binary data in an URL.
> St.Ack


View raw message