> Thanks guys for the replies. Is there any difference if I use json
> representation (application/json)?
Key, column, and value will also be base64 encoded if using JSON representation
> Can I get data is plain text with the special characters
> escaped in some way?
I could add a text/plain representation option that would send back ruby-style
escaped text data if this would be useful to you. (This is what our
Bytes.toBinaryString() helper produces.)
Best regards,
- Andy
Problems worthy of attack prove their worth by hitting back. - Piet Hein (via
Tom White)
--- On Thu, 2/3/11, Hari Sreekumar <[email protected]> wrote:
> From: Hari Sreekumar <[email protected]>
> Subject: Re: Queries regarding REST API
> To: [email protected], [email protected]
> Date: Thursday, February 3, 2011, 1:10 AM
> Thanks guys for the replies. Is there
> any difference if I use json
> representation (application/json)? Can I get another
> encoding if I go that
> way? Can I get data is plain text with the special
> characters escaped in
> some way?
>
> hari
>
> On Wed, Feb 2, 2011 at 1:50 AM, Andrew Purtell <[email protected]>
> wrote:
>
> > > 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 <[email protected]>
> wrote:
> >
> > > From: Stack <[email protected]>
> > > Subject: Re: Queries regarding REST API
> > > To: [email protected]
> > > Date: Tuesday, February 1, 2011, 11:21 AM
> > > On Tue, Feb 1, 2011 at 10:57 AM, Hari
> > > Sreekumar
> > > <[email protected]>
> > > 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
> > >
> >
> >
> >
> >
>
