Thanks Andrew. I didnt to change behavior of hbase shell. I intend to
provide an enhancement to HBase Rest while not impacting its default
behavior.
On Thu, Aug 6, 2015 at 5:29 PM, Andrew Purtell wrote:
> > returned from the shell
>
> Meant "returned from the REST gateway".
>
>
> On Thu, Aug 6,
> returned from the shell
Meant "returned from the REST gateway".
On Thu, Aug 6, 2015 at 5:28 PM, Andrew Purtell wrote:
> Unfortunately we can't change the current set of representations are
> returned from the shell, that would be a backwards compatibility problem.
> We can however add new re
Unfortunately we can't change the current set of representations are
returned from the shell, that would be a backwards compatibility problem.
We can however add new representations (selectable by way of the Accept
header, e.g. Accept: text/plain). If you'd like to propose a patch we'd
certainly lo
Hi Andrew,
Thanks for sharing your thoughts. Sorry for late reply as i recently came
back from vacation.
I understand that HBase stores byte arrays, so its hard for HBase to figure
out the data type.
What if, the client knows that all the columns in the Rest request are
Strings. In that case, can
The closest you can get to just a string is have your client use an accept
header of "Accept: application/octet-stream" with making a query. This will
return zero or one value in the response. If a value is present in the
table at the requested location, the response body will be the unencoded
Hi All,
We have a String Rowkey. We have String values of cells.
Still, Stargate returns the data with Base64 encoding due to which a user
cant read the data. Is there a way to disable Base64 encoding and then Rest
request would just return Strings.
--
Thanks & Regards,
Anil Gupta
