[
https://issues.apache.org/jira/browse/FLINK-19828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-19828:
-----------------------------------
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.
> Allow loading multiple configuration files
> ------------------------------------------
>
> Key: FLINK-19828
> URL: https://issues.apache.org/jira/browse/FLINK-19828
> Project: Flink
> Issue Type: New Feature
> Components: Runtime / Configuration
> Affects Versions: 1.12.0
> Reporter: Robert Metzger
> Priority: Minor
> Labels: auto-deprioritized-major, stale-minor
>
> This is a feature request from the mailing list:
> https://lists.apache.org/thread.html/r84ad3af6585ba8138d8bfa8d3d391dab9017aace52df8a757989be1e%40%3Cuser.flink.apache.org%3E
> For scenarios where you want to deploy Flink (for example on Kubernetes) with
> a set of common configuration keys (for example for the file system), and
> some deployment specific configuration keys (for example savepoint location),
> it would be helpful if Flink had a mechanism for loading multiple
> configuration files.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
