[ 
https://issues.apache.org/jira/browse/FLINK-31335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Flink Jira Bot updated FLINK-31335:
-----------------------------------
    Labels: pull-request-available stale-assigned  (was: pull-request-available)

I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help 
the community manage its development. I see this issue is assigned but has not 
received an update in 30 days, so it has been labeled "stale-assigned".
If you are still working on the issue, please remove the label and add a 
comment updating the community on your progress.  If this issue is waiting on 
feedback, please consider this a reminder to the committer/reviewer. Flink is a 
very active project, and so we appreciate your patience.
If you are no longer working on the issue, please unassign yourself so someone 
else may work on it.


> using sql-gateway to submit job to yarn cluster, sql-gateway don't support 
> kerberos
> -----------------------------------------------------------------------------------
>
>                 Key: FLINK-31335
>                 URL: https://issues.apache.org/jira/browse/FLINK-31335
>             Project: Flink
>          Issue Type: Improvement
>          Components: Table SQL / Gateway
>    Affects Versions: 1.16.0
>            Reporter: felixzh
>            Assignee: felixzh
>            Priority: Major
>              Labels: pull-request-available, stale-assigned
>             Fix For: 1.17.2
>
>
> when submit job to yarn cluster, sql-gateway don't support kerberos.
> 1. yarn-per-job mode
> -Dexecution.target=yarn-per-job
> 2. yarn-session mode
> -Dexecution.target=yarn-session -Dyarn.application.id=yarnSessionAppID(eg: 
> application_1677479737242_0052)
> sql-gateway need to use SecurityUtils Modules.
> default use flink-conf.yaml(security.kerberos.login.principal and 
> security.kerberos.login.keytab), also support 
> -Dsecurity.kerberos.login.keytab and -Dsecurity.kerberos.login.principal (eg: 
> 1/2)



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to