Hi Jack,
There are three representations the REST server can return, selectable by the
client via the Accept header:
text/xml: XML representation, base64 encoding of data
application/x-protobuf: pbuf representation, see the *.proto files
application/octet-stream: plain binary
It's the last one you want obviously.
A limitation with application/octet-stream is only one value can be retrieved
or stored at a time using that representation. (In contrast, the others can
return complex object hierarchies of multiple versions, multiple columns,
multiple rows.)
As you may know HBase table schemas support getting and setting arbitrary
attributes on them. We can introduce an attribute for column families that can
instruct the REST gateway to perform data encoding translation, with
base64->binary as the first supported option.
If you only require one value returned per GET then we can stop here.
Best regards,
- Andy
> From: Jack Levin
> Subject: Re: question about base64
>
> decode base64 into raw/binary on the way out please
>
> -Jack
>
>
> On Oct 16, 2010, at 2:39 PM, Ryan Rawson wrote:
>
> > decode base64 into raw/binary on the way out?
