You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "Keith Turner (JIRA)" <ji...@apache.org> on 2012/11/21 23:42:58 UTC
[jira] [Created] (ACCUMULO-869) Determine best default classloader
hierarchy
Keith Turner created ACCUMULO-869:
-------------------------------------
Summary: Determine best default classloader hierarchy
Key: ACCUMULO-869
URL: https://issues.apache.org/jira/browse/ACCUMULO-869
Project: Accumulo
Issue Type: Sub-task
Reporter: Keith Turner
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
[jira] [Commented] (ACCUMULO-869) Determine best default
classloader hierarchy
Posted by "Keith Turner (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ACCUMULO-869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13502388#comment-13502388 ]
Keith Turner commented on ACCUMULO-869:
---------------------------------------
By default I think we should make the system context a parent of all user context. This way a user would only need to put jar containing their iterators in their context. Could make this configurable if a user wants to do something more advanced.
> 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
> Fix For: 1.5.0
>
>
> 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
[jira] [Commented] (ACCUMULO-869) Determine best default
classloader hierarchy
Posted by "Dave Marion (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ACCUMULO-869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13507792#comment-13507792 ]
Dave Marion commented on ACCUMULO-869:
--------------------------------------
Did the following in the patch:
added new property
changed constant name from DEFAULT_CONTEXT to SYSTEM_CONTEXT
updated javadoc
> 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
[jira] [Assigned] (ACCUMULO-869) Determine best default classloader
hierarchy
Posted by "Dave Marion (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ACCUMULO-869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dave Marion reassigned ACCUMULO-869:
------------------------------------
Assignee: Dave Marion
> 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
>
>
> 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
[jira] [Commented] (ACCUMULO-869) Determine best default
classloader hierarchy
Posted by "Dave Marion (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ACCUMULO-869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13506947#comment-13506947 ]
Dave Marion commented on ACCUMULO-869:
--------------------------------------
I think we should add a new property, something like classloader.vfs.context.classpath.isolation, which will default to false. In the default state, the user defined context classloaders will be a child of the system context classloader. If set to true, then the user defined context classloader will be a sibling of the system context classloader.
> 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
> Fix For: 1.5.0
>
>
> 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
[jira] [Updated] (ACCUMULO-869) Determine best default classloader
hierarchy
Posted by "Dave Marion (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ACCUMULO-869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dave Marion updated ACCUMULO-869:
---------------------------------
Attachment: ACCUMULO-869-1.patch
> 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