[
https://issues.apache.org/jira/browse/ACCUMULO-869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13531891#comment-13531891
]
Dave Marion commented on ACCUMULO-869:
--------------------------------------
bq. •If isolation is enabled, should the parent classloader be the java system
classloader, instead of the classloader that pulls stuff from $ACCUMULO_HOME/lib
I would say no as I believe it also references $HADOOP_HOME and $ZK_HOME
bq. •Should isolation be configurable per context?
We could do that, but it would likely increase complexity a lot. It would be
one more thing to track and manage. I'm not against it.
> Determine best default classloader hierarchy
> ---------------------------------------------
>
> Key: ACCUMULO-869
> URL: https://issues.apache.org/jira/browse/ACCUMULO-869
> Project: Accumulo
> Issue Type: Sub-task
> Components: start
> Reporter: Keith Turner
> Assignee: Dave Marion
> Fix For: 1.5.0
>
> Attachments: ACCUMULO-869-1.patch
>
>
> A user created context classloader in the current patch does not have the
> system context as it parent. If the system context contained Accumulo jars,
> then the user context would have to add its own Accumulo jars. The drawback
> of this is that the user context may use a different version of accumulo jars
> than the system context leading to unexpected behavior. The advantage of
> this is that user context could load newer jars. For example, if Accumulo
> depended on an old json library the user context could load a newer version
> with no problems.
--
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
