Your last point was exactly what I was looking for. I am thinking about
using attributes along with coprocessors to impose some application-level
authorization constraints. For example, in a get, I can pass username and
credential attributes and have the coprocessor filter results based on some
rules or group membership. Of course, I'll need to make sure that that
step doesn't violate regular good practices for coprocessors. If anyone
has used attributes for any similar purpose, I'd be interested in hearing
about those experiences.
On Fri, Feb 22, 2013 at 4:24 PM, Harsh J <[EMAIL PROTECTED]> wrote:
> The attributes are serialized along with the base operation request.
> There's perhaps no immediate client-side usage of this, it is used by
> the Mutation class to set a cluster ID in HBase's Replication context:
> I suppose it could also be used to tag client requests, and used along
> with Coprocessors that way for some behavior differences.
> On Sat, Feb 23, 2013 at 12:11 AM, Toby Lazar <[EMAIL PROTECTED]> wrote:
> > What is the purpose of the getAttribute and setAttribute methods for
> > classes implementing OperationWithAttributes? I don't see much
> > documentation about them, haven't seen much discussion on this list about
> > them, and am wondering what people use them for. Or, are they mostly
> > used internally? Any insights about these methods are appreciated.
> > Thanks!
> > Toby
> Harsh J