> Since there are no HBase ACLs
This is true only until HBASE-3025 is ready and goes in, post 0.92. It may not
be of immediate help now but yes HBase will have ACLs. They are on the 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 <[email protected]> wrote:
> From: Barney Frank <[email protected]>
> Subject: Re: any multitenancy suggestions for HBase?
> To: [email protected], [email protected]
> Date: Tuesday, June 14, 2011, 5:04 AM
> 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
> authorized within our app.
>
> On Mon, Jun 13, 2011 at 5:31 PM, Bill Graham <[email protected]>
> wrote:
>
> > 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
> looking to propose a
> > simple convention that will hopefully keep people from
> stepping on each
> > others toes (or worse!).
> >
> > Does anyone have any best/worst practices they're
> willing to share w.r.t.
> > thing likes table/column naming schemes in a
> multitenant environment? For
> > table names for example, is there anything better than
> a basic
> > dot-delimited
> > naming convention with the group name as the first
> token?
> >
> > Also, I assume there's no performance cost with using
> long table names like
> > there is with long CF:col names. Please let me know if
> that's not the case.
> >
> > thanks,
> > Bill
> >
>
