Whoops, I hit send before considering the other meaning of overhead, sorry.
Can't say yet, probably not much, but will profile.
Best regards,
- Andy
--- On Mon, 10/18/10, Andrew Purtell wrote:
> From: Andrew Purtell
> Subject: Re: question about base64
> To: "Jack
> From: Jack Levin
[...]
> base64->binary is exactly what we
> need and one GET value only , what is the expected overhead
> ? Probably minor , yes?
Here's what I get:
> GET /images/718394072614491.jpg/content HTTP/1.1
> User-Agent: curl/7.21.0 (x86_64-pc-linux-gnu) libcurl/7.21.0 OpenSSL/0.9.8o
base64->binary is exactly what we need and one GET value only , what is the
expected overhead ? Probably minor , yes?
-Jack
On Oct 16,ex 2010, at 4:28 PM, Andrew Purtell wrote:
> base64->binary
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?
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?
Hi,
Right now the regionserver does not do any interpretation of the data
sent to it. The only "exception" is that we lexographically sort the
rows, families and qualifiers, using a byte-by-byte comparison.
Are you looking to send to the regionserver base64 and have it stored
as raw/binary? Or
If I have base64 encoded binary files in hbase columns, is it possible
to instruct the regionserver to decode it to binary and give it back
to me in binary format? I am interesting it reading via REST server.
-Jack
