You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Flink Jira Bot (Jira)" <ji...@apache.org> on 2021/11/05 22:40:01 UTC
[jira] [Updated] (FLINK-17650) Impossible to set Security related
configs as dynamic properties
[ https://issues.apache.org/jira/browse/FLINK-17650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Flink Jira Bot updated FLINK-17650:
-----------------------------------
Labels: auto-deprioritized-major stale-minor (was: auto-deprioritized-major)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help the community manage its development. I see this issues has been marked as Minor but is unassigned and neither itself nor its Sub-Tasks have been updated for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is still Minor, please either assign yourself or give an update. Afterwards, please remove the label or in 7 days the issue will be deprioritized.
> Impossible to set Security related configs as dynamic properties
> ----------------------------------------------------------------
>
> Key: FLINK-17650
> URL: https://issues.apache.org/jira/browse/FLINK-17650
> Project: Flink
> Issue Type: Bug
> Components: Command Line Client
> Reporter: Gyula Fora
> Priority: Minor
> Labels: auto-deprioritized-major, stale-minor
>
> The CliFrontend installs the Security context based on the cli.configuration (CliFrontend#L985)which does not take into account dynamic properties (such as -yD or -D depending on the executor)
> This makes it impossible for instance to configure kerberos by setting these configs as dynamic props.
> We should first apply all the extra configs before installing the security context and running the command.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)