You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@samza.apache.org by "Navina Ramesh (JIRA)" <ji...@apache.org> on 2016/03/08 21:05:40 UTC
[jira] [Commented] (SAMZA-697) Isolate Class Loader for user
implemented Tasks
[ https://issues.apache.org/jira/browse/SAMZA-697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15185674#comment-15185674 ]
Navina Ramesh commented on SAMZA-697:
-------------------------------------
[~boryas] What is the status of this JIRA? Are you working on the existing patch or are you going to provide a new one?
> Isolate Class Loader for user implemented Tasks
> -----------------------------------------------
>
> Key: SAMZA-697
> URL: https://issues.apache.org/jira/browse/SAMZA-697
> Project: Samza
> Issue Type: Bug
> Reporter: Guozhang Wang
> Assignee: Boris Shkolnik
> Attachments: SAMZA-697.v1.patch, SAMZA-697.v2.patch
>
>
> Today we use a single class loader for both framework classes as well as user code (StreamTask implementations), which could result in conflicts of dependencies.
> The approach is to use separate class loaders for framework classes and user instantiated classes. This approach has also been applied in Hadoop and Spark (MAPREDUCE-1700, SPARK-1870).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)