accumulo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dave Marion (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-708) Modify ClassLoader to support different applications / multi-tenancy
Date Mon, 06 Aug 2012 23:50:02 GMT


Dave Marion commented on ACCUMULO-708:

Documenting thoughts: Seems that there are only two contexts in which this applies: table
operations (in which there is no user) and client operations (in which there is a user perform
scan or update). The current classloader (be default) uses the boot classloader with a child
classloader reading from $ACCUMULO_HOME/lib and a grandchild classloader reading from $ACCUMULO_HOME/lib/ext.

We would need a way for the classloader to discover either the table name or the current user
when loadClass is called in the thread. This is currently the part that I am not sure of.
Need input from others and to look at the code more.
> Modify ClassLoader to support different applications / multi-tenancy
> --------------------------------------------------------------------
>                 Key: ACCUMULO-708
>                 URL:
>             Project: Accumulo
>          Issue Type: Improvement
>          Components: start
>    Affects Versions: 1.5.0
>            Reporter: Dave Marion
>            Assignee: Dave Marion
>              Labels: classloader
>   Original Estimate: 24h
>  Remaining Estimate: 24h
> I'd like to expand the current classloader to support loading classes from HDFS and different
application contexts. I'll be modifying the ticket as the idea matures.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message