You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@samza.apache.org by "Jake Maes (JIRA)" <ji...@apache.org> on 2017/04/26 16:07:04 UTC
[jira] [Resolved] (SAMZA-1233) Fix SamzaTaskProxy system admin
instantiation
[ https://issues.apache.org/jira/browse/SAMZA-1233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jake Maes resolved SAMZA-1233.
------------------------------
Resolution: Fixed
Fix Version/s: 0.13.0
Issue resolved by pull request 138
[https://github.com/apache/samza/pull/138]
> Fix SamzaTaskProxy system admin instantiation
> ---------------------------------------------
>
> Key: SAMZA-1233
> URL: https://issues.apache.org/jira/browse/SAMZA-1233
> Project: Samza
> Issue Type: Task
> Reporter: Shanthoosh Venkataraman
> Assignee: Shanthoosh Venkataraman
> Priority: Minor
> Fix For: 0.13.0
>
>
> SamzaTaskProxy instantiates all SystemAdmin classes defined in
> job configuration.
> This is unnecessary and sometimes leads to ClassNotFoundException when different SystemAdmin(HdfsSystemAdmin, ElasticSearchAdmin) classes are not available in classpath during samza-rest deployment and introduces library dependency from all system modules (samza-kakfa, samza-hdfs etc)directly into samza-rest.
> To solve this problem, instantiate SystemAdmin for job coordinator alone in SamzaTaskProxy.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)