accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Keith Turner (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-867) Support common use cases for loading classes from context (e.g. HDFS)
Date Fri, 14 Dec 2012 01:08:27 GMT


Keith Turner commented on ACCUMULO-867:

For table classpaths I was concerned about how an Accumulo adminstrator could control what
code was introduced into the system.   Was discussing this with Dave Marion and he suggested
having per table classpaths reference context.  Do this instead of directly specifying URIs
as shown in the issue description.  Context would be defined through system properties and
therefore not just anyone with ALTER_TABLE could modify them.   Inorder to make this convenient,
would need to modify how the current code works so that context config can be stored in zookeeper.
 The current code only reads context config from accumulo-site.xml.  

So inorder to setup a per table classpath, a user would set a system property like the following.


and then set a per table property


> Support common use cases for loading classes from context (e.g. HDFS)
> ---------------------------------------------------------------------
>                 Key: ACCUMULO-867
>                 URL:
>             Project: Accumulo
>          Issue Type: Sub-task
>          Components: start
>            Reporter: Keith Turner
>             Fix For: 1.5.0
> We need to decide how want to make this new classloader functionality available to users.
> One use case is making per-table class loaders availiable.   This would allow the user
to set a per table property like the following.
> {noformat}
>    table.classpath=hdfs://nn:8092/myApp
> {noformat}
> Setting this would allow iterators specific to the table to be loaded from a given location.
  Currently when a user iterator is placed in lib/ext all tables see the iterator.
> Another possible use case is per-scan classpath. 

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

View raw message