[
https://issues.apache.org/jira/browse/YARN-6771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16093116#comment-16093116
]
Sangjin Lee commented on YARN-6771:
-----------------------------------
Do you have a JIRA on the Zeppelin side that describes the actual issue? I
suppose this is an issue when you need to load a class (that is only on your
classpath) dynamically via {{Configuration}}?
Could you please update your patch to include {{RpcServerFactoryPBImpl}} too?
Although the client alone would address your issue, from the YARN perspective,
it would not be ideal to have an asymmetric behavior.
I think we also need to run a wider test suite than what jenkins runs out of
the change analysis to ensure nothing changes as a result...
> Use classloader inside configuration class to make new classes
> ---------------------------------------------------------------
>
> Key: YARN-6771
> URL: https://issues.apache.org/jira/browse/YARN-6771
> Project: Hadoop YARN
> Issue Type: Bug
> Affects Versions: 2.8.1, 3.0.0-alpha4
> Reporter: Jongyoul Lee
> Fix For: 2.8.2
>
> Attachments: YARN-6771-1.patch, YARN-6771-2.patch, YARN-6771.patch
>
>
> While running {{RpcClientFactoryPBImpl.getClient}},
> {{RpcClientFactoryPBImpl}} uses {{localConf.getClassByName}}. But in case of
> using custom classloader, we have to use {{conf.getClassByName}} because
> custom classloader is already stored in {{Configuration}} class.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
