[jira] [Comment Edited] (KYLIN-1014) Support kerberos authentication while getting status from RM

["Dong Li (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/KYLIN-1014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15281272#comment-15281272 ] 

Dong Li edited comment on KYLIN-1014 at 5/12/16 7:20 AM:
---------------------------------------------------------

Patch merged on master branch(will release as 1.5.2), please have a check, and resolve this JIRA if could.


was (Author: lidong_sjtu):
Patch merged, please have a check, and resolve this JIRA if could.

> Support kerberos authentication while getting status from RM
> ------------------------------------------------------------
>
>                 Key: KYLIN-1014
>                 URL: https://issues.apache.org/jira/browse/KYLIN-1014
>             Project: Kylin
>          Issue Type: Improvement
>          Components: Job Engine
>    Affects Versions: v1.0, v0.7.2, v0.7.1
>            Reporter: fengYu
>            Assignee: Shaofeng SHI
>             Fix For: v1.4.0, v1.3.0
>
>         Attachments: 0001-KYLIN-1014-error-while-retry-rm-master.patch, 0001-hadoop-status-checker-support-rm-with-kerberos.patch, patch-for-2.0-rc.patch
>
>
> I have used kylin-0.7.2 build cube and do some query, and I am trying kylin-1.0 in another hadoop cluster. I get this problem below in kylin-0.7.2 and kylin-1.0 :
> Our hadoop cluster deals with authentication with kerberos, However, We find after submit a mapreduce job(the second step in building cube), kylin will send a http request to RM server and get the job status at regular intervals, But we always get errors here because kylin do nothing about kerberos. Finally , we do some change on source code and make it support kerberos authentication . attachment is my patch file..
> I add a property named "kylin.job.status.with.kerberos" which means if we need do authentication with kerberos when getting status from RM, the default value is false.
> It will be highly appreciated if you have some good idea or some suggestion. Thanks...



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)