[
https://issues.apache.org/jira/browse/ACCUMULO-708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13493618#comment-13493618
]
Dave Marion commented on ACCUMULO-708:
--------------------------------------
bq. •use general prefix for new config properties. general denotes its a
configuration for all services (i.e. master, tserver, etc)
I'll include in another patch, I'll wait for your other comments and roll all
the changes up into a new patch.
bq. •needs documentation. How does a user know this feature exists and what
they can do with it?
Where should this be documented? User guide, readme, etc?
bq. •probably should not use org/apache/commons/vfs2 package. If the commons
project defines classes with same name and user loads Accumulo and Commons jar
chaos could ensue.
Understood. I know for a fact that these classes don't collide with ones in
Commons VFS. Code has also been submitted to VFS for inclusion in a
future release (VFS-442).
bq. •I noticed there were a few accumulo site files introduced. Are these for
testing? Some of them configured walog dirs which is no longer nesc in 1.5.
These are there for tests. I believe I copied the 512MB example site file and
modified for my tests. The walog property is not used and the test will not
fail if the directory does not exist as the servers are not started during the
tests.
> Modify ClassLoader to support different applications / multi-tenancy
> --------------------------------------------------------------------
>
> Key: ACCUMULO-708
> URL: https://issues.apache.org/jira/browse/ACCUMULO-708
> Project: Accumulo
> Issue Type: Improvement
> Components: start
> Reporter: Dave Marion
> Assignee: Dave Marion
> Labels: classloader
> Fix For: 1.5.0
>
> Attachments: ACCUMULO-708-1.patch
>
> Original Estimate: 24h
> Time Spent: 33h
> Remaining Estimate: 0h
>
> 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
For more information on JIRA, see: http://www.atlassian.com/software/jira
