[
https://issues.apache.org/jira/browse/FLINK-16809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-16809:
-----------------------------------
Labels: auto-deprioritized-major auto-deprioritized-minor
pull-request-available (was: auto-deprioritized-major pull-request-available
stale-minor)
Priority: Not a Priority (was: Minor)
This issue was labeled "stale-minor" 7 days ago and has not received any
updates so it is being deprioritized. If this ticket is actually Minor, please
raise the priority and ask a committer to assign you the issue or revive the
public discussion.
> Support setting CallerContext on YARN deployments
> -------------------------------------------------
>
> Key: FLINK-16809
> URL: https://issues.apache.org/jira/browse/FLINK-16809
> Project: Flink
> Issue Type: Improvement
> Components: Deployment / YARN
> Reporter: Qi Zhu
> Priority: Not a Priority
> Labels: auto-deprioritized-major, auto-deprioritized-minor,
> pull-request-available
>
> Now the Spark and hive have the Call Context to meet the HDFS Job Audit
> requirement.
> I think the flink also should to add it, and in our cluster the flink job may
> have big pressure to the HDFS, it's will be helpful to find the root job.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
