[ https://issues.apache.org/jira/browse/KYLIN-3866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16791575#comment-16791575 ]
Shaofeng SHI commented on KYLIN-3866: ------------------------------------- Now I know the problem, thank you for the information! The change will be good; I see you add a config parameter to keep the old behavior, is that parameter is necessary? I mean, if the "mapreduce.application.classpath" is absent, can we just let it go (totally not get the classpath from local configuration)? > Whether to set mapreduce.application.classpath is determined by the user > ------------------------------------------------------------------------ > > Key: KYLIN-3866 > URL: https://issues.apache.org/jira/browse/KYLIN-3866 > Project: Kylin > Issue Type: Bug > Reporter: Guangxu Cheng > Priority: Major > Attachments: KYLIN-3866.master.001.patch > > > In the kylin environment, if there is no configuration parameter > "mapreduce.application.classpath", then kylin will use the command "mapred > classpath" to get the local classpath and set it to > "mapreduce.application.classpath", However, it will cause the following two > problems: > 1. The local classpath may not be the same as the MapReduce cluster. > 2. There is no need to configure the parameter > "mapreduce.application.classpath" on the client side in some cluster. > So, it may be a better choice for users to decide whether they need to > configure this parameter or not. -- This message was sent by Atlassian JIRA (v7.6.3#76005)