hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jongyoul Lee (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-6771) Use classloader inside configuration class to make new classes
Date Sun, 09 Jul 2017 10:40:03 GMT

    [ https://issues.apache.org/jira/browse/YARN-6771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16079540#comment-16079540

Jongyoul Lee commented on YARN-6771:

It's related to classloader and its usage. To make a test case, we need class that is not
included in default class loader it means we need to make a class in order not to be included
when running test. I'm not sure what the best way is, but one possible way is to make a class
dynamically when starting test. May I use that way to test it?

> 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
>            Reporter: Jongyoul Lee
>             Fix For: 2.8.2
>         Attachments: 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

To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org

View raw message