flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Flink Jira Bot (Jira)" <j...@apache.org>
Subject [jira] [Updated] (FLINK-22347) Support renaming shipped archives on Yarn
Date Wed, 19 May 2021 22:56:03 GMT

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

Flink Jira Bot updated FLINK-22347:
    Labels: stale-major  (was: )

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 Major but is unassigned and neither
itself nor its Sub-Tasks have been updated for 30 days. I have gone ahead and added a "stale-major"
to the issue". If this ticket is a Major, please either assign yourself or give an update.
Afterwards, please remove the label or in 7 days the issue will be deprioritized.

> Support renaming shipped archives on Yarn
> -----------------------------------------
>                 Key: FLINK-22347
>                 URL: https://issues.apache.org/jira/browse/FLINK-22347
>             Project: Flink
>          Issue Type: Improvement
>          Components: Deployment / YARN
>    Affects Versions: 1.12.2, 1.13.0
>            Reporter: Yang Wang
>            Priority: Major
>              Labels: stale-major
> Currently, Flink supports to ship archives via {{yarn.ship-archives}}. However, it is impossible
to rename the unzipped directory of these archives.
> We just need to use "#" for the renaming. For example, {{python_3_with_flink.tar.gz#environment}}.
The unzipped directory will be renamed to environment.
> Some other distributed frameworks(e.g. hadoop mapreduce, spark) also have the similar

This message was sent by Atlassian Jira

View raw message