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

Flink Jira Bot updated FLINK-18211:
-----------------------------------
    Labels: auto-unassigned pull-request-available stale-major  (was: 
auto-unassigned 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 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.


> Dynamic properties setting 'pipeline.jars' will be overwritten
> --------------------------------------------------------------
>
>                 Key: FLINK-18211
>                 URL: https://issues.apache.org/jira/browse/FLINK-18211
>             Project: Flink
>          Issue Type: Bug
>          Components: Client / Job Submission
>    Affects Versions: 1.10.0, 1.11.0
>            Reporter: Echo Lee
>            Priority: Major
>              Labels: auto-unassigned, pull-request-available, stale-major
>             Fix For: 1.14.0
>
>
> When we submit the application through "flink run 
> -Dpipeline.jars='/user1.jar, user2.jar'..." command,  configuration will 
> include 'pipeline.jars', But ExecutionConfigAccessor#fromProgramOptions will 
> be reset this property, So the property set by the user is invalid.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to