[
https://issues.apache.org/jira/browse/HADOOP-13070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15264412#comment-15264412
]
Sangjin Lee commented on HADOOP-13070:
--------------------------------------
Hi [[email protected]], I'm not quite sure what you meant by flipping the
maven switch. Could you kindly elaborate?
This is a companion to HADOOP-11656, but this addresses more of a
container-like situation (e.g. isolating user code in MR tasks, etc.). There
are some long-standing improvements we can make that will make everyone's life
easier but which may break some backward compatibility. I'm thinking of
changing some APIs and replacing configs, etc.
I'm not sure if this should target Hadoop 3 (I'm not entirely clear where we
stand with Hadoop 3 at the moment). My hope is it would be in the first release
where breaking backward compatibility is allowed.
> classloading isolation improvements for cleaner and stricter dependencies
> -------------------------------------------------------------------------
>
> Key: HADOOP-13070
> URL: https://issues.apache.org/jira/browse/HADOOP-13070
> Project: Hadoop Common
> Issue Type: Improvement
> Components: util
> Reporter: Sangjin Lee
> Assignee: Sangjin Lee
> Priority: Critical
>
> Related to HADOOP-11656, we would like to make a number of improvements in
> terms of classloading isolation so that user-code can run safely without
> worrying about dependency collisions with the Hadoop dependencies.
> By the same token, it should raised the quality of the user code and its
> specified classpath so that users get clear signals if they specify incorrect
> classpaths.
> This will contain a proposal that will include several improvements some of
> which may not be backward compatible. As such, it should be targeted to the
> next major revision of Hadoop.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
