>> > more isolated or postfixed if you want them sharing the same grid more
>> and
>> > more.
>> >
>> > We had some shared tables that are not postfixed nor prefixed and are
>> only
>> > touched by a committee when needed for everyone...obviously tr
Hi Bill,
> From: Bill Graham
> Andy, I can see value in having ACLs on a per-column-pattern (or
> maybe just per-prefix to make multiple pattern conflict resolution
> simpler) basis. I know this isn't in scope for the initial release,
> but would the current design lend itself to be extended for
gt; touched by a committee when needed for everyone...obviously tradeoff in
> > doing that.
> >
> > Later,
> > Dean
> >
> > -----Original Message-
> > From: Otis Gospodnetic [mailto:otis_gospodne...@yahoo.com]
> > Sent: Friday, June 17, 2011 9:55 P
day, June 17, 2011 9:55 PM
> To: user@hbase.apache.org; billgra...@gmail.com
> Subject: Re: any multitenancy suggestions for HBase?
>
> Hi Bill,
>
> At the recent HBase hackathon in Berlin there was some word of ACLs in (the
> next release of?) HBase from the Trend Micro guys,
: Monday, June 13, 2011 6:31 PM
>Subject: any multitenancy suggestions for HBase?
>
>Hello there,
>
>We have a number of different groups within our organization who will soon
>be working within the same HBase cluster and we're trying to set up some
>best practices to keep t
ngineers with interest in Big Data
Mining and Analytics
http://blog.sematext.com/2011/04/18/hiring-data-mining-analytics-machine-learning-hackers/
>
>From: Bill Graham
>To: hbase-u...@hadoop.apache.org
>Sent: Monday, June 13, 2011 6:31 PM
>Subject: any
he
> roadmap.
>
> Best regards,
>
>- Andy
>
> Problems worthy of attack prove their worth by hitting back. - Piet Hein
> (via Tom White)
>
>
> --- On Tue, 6/14/11, Barney Frank wrote:
>
> > From: Barney Frank
> > Subject: Re: any multitenancy sugge
ein (via
Tom White)
--- On Tue, 6/14/11, Barney Frank wrote:
> From: Barney Frank
> Subject: Re: any multitenancy suggestions for HBase?
> To: user@hbase.apache.org, billgra...@gmail.com
> Date: Tuesday, June 14, 2011, 5:04 AM
> Our implementation supports multiple
> customer
Our implementation supports multiple customers that share the same tables
and column families. We use the customerId as the first token of the Row Id
i.e. "CUST123|someOtherRowQualifier". For all customer queries, we add
their customerId as the row prefix and, of course, ensure that they are
auth
Hello there,
We have a number of different groups within our organization who will soon
be working within the same HBase cluster and we're trying to set up some
best practices to keep thinks organized. Since there are no HBase ACLs and
no concept of multiple databases in the cluster, we're lookin
10 matches
Mail list logo
