Hi,
We are using HBase 0.94 and Hadoop 2.0.0 .We are using CDH 4.7
We have a 4 node cluster with one master and the 3 region servers
We Have time series data. We have row key with the format of
Reversetimestamp_id. We have client connection timeout in the modules and
constantly facin
Hi, all:
Not long ago, I wanted to test Cell-Level ACLs by using tags and use the
class "ExpAsStringVisibilityLabelServiceImpl" instead of the default class
"DefaultVisibilityLabelServiceImpl". set as fllows in hbase-site.xml. My HBase
version is 0.99.2.
But when I restarted my cluster, t
This looks like a bug.
Mind filing an issue and attach your patch ?
Thanks
On Sun, Feb 1, 2015 at 11:13 PM, 15810705424 <15810705...@163.com> wrote:
> Hi, all:
> Not long ago, I wanted to test Cell-Level ACLs by using tags and use
> the class "ExpAsStringVisibilityLabelServiceImpl" instead
Hi
Just for confirmation - you are trying to use cell level visibility tags -
correct? Cell Level ACLs are different from visibility tags.
Coming to ExpAsStringVisibilityLabelServiceImpl - it is currently a test
implementation and not a real src implementation. The idea for this class
is to show
Hey Joseph,
I suspect you're hitting hotspotting (see
http://hbase.apache.org/book.html#rowkey.design). Moving forward, you might
want to consider something like OpenTSDB for your time series data.
-Dima
On Mon, Feb 2, 2015 at 1:18 AM, joseph wrote:
> Hi,
>
>
>
> We are using HBase 0.94 and Ha
Hi,
All the default scan label generators uses the VisibilityLabelCache to get
user labels somewhere. But the VisibilityLableCache implementation is for
the DefaultVisibilityLabelServiceImpl mostly.
Even if we add the method createAndGet() for the VisibilityLableCache
to ExpAsStringVisibilityLabe
Hi,
There is a SimpleScanLabelGenerator in the package. This is works with
ExpAsStringVisibilityLabelServiceImpl. And it is used in the unit test for
ExpAsStringVisibilityLabelServiceImpl.
Jerry
On Mon, Feb 2, 2015 at 10:54 AM, Jerry He wrote:
> Hi,
>
> All the default scan label generators u
What is the rest service returning to you? It should be the base64 encoded
value. You'll need to decode this value to get a byte[] with which you can
operate. As for exactly how to parse it, that depends on how you created it
in the first place.
The section on REST in the community book [0] links
