[jira] [Updated] (FLINK-23620) Introduce proper YAML parsing to Flink's configuration
[
https://issues.apache.org/jira/browse/FLINK-23620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Weijie Guo updated FLINK-23620:
---
Labels: 2.0-related (was: pull-request-available stale-assigned)
> Introduce proper YAML parsing to Flink's configuration
> --
>
> Key: FLINK-23620
> URL: https://issues.apache.org/jira/browse/FLINK-23620
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Configuration
>Reporter: Mika Naylor
>Assignee: Junrui Li
>Priority: Minor
> Labels: 2.0-related
> Fix For: 2.0.0
>
>
> At the moment, the YAML parsing for Flink's configuration file
> ({{conf/flink-conf.yaml)}} is pretty basic. It only supports basic key value
> pairs, such as:
> {code:java}
> a.b.c: a value
> a.b.d: another value{code}
> As well as supporting some invalid YAML syntax, such as:
> {code:java}
> a: b: value{code}
>
> Introducing proper YAML parsing to the configuration component would let
> Flink users use features such as nested keys, such as:
> {code:java}
> a:
> b:
> c: a value
> d: another value{code}
> as well as make it easier to integrate configuration tools/languages that
> compile to YAML, such as Dhall.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FLINK-23620) Introduce proper YAML parsing to Flink's configuration
[
https://issues.apache.org/jira/browse/FLINK-23620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xintong Song updated FLINK-23620:
-
Fix Version/s: 2.0.0
> Introduce proper YAML parsing to Flink's configuration
> --
>
> Key: FLINK-23620
> URL: https://issues.apache.org/jira/browse/FLINK-23620
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Configuration
>Reporter: Mika Naylor
>Assignee: Junrui Li
>Priority: Minor
> Labels: pull-request-available, stale-assigned
> Fix For: 2.0.0
>
>
> At the moment, the YAML parsing for Flink's configuration file
> ({{conf/flink-conf.yaml)}} is pretty basic. It only supports basic key value
> pairs, such as:
> {code:java}
> a.b.c: a value
> a.b.d: another value{code}
> As well as supporting some invalid YAML syntax, such as:
> {code:java}
> a: b: value{code}
>
> Introducing proper YAML parsing to the configuration component would let
> Flink users use features such as nested keys, such as:
> {code:java}
> a:
> b:
> c: a value
> d: another value{code}
> as well as make it easier to integrate configuration tools/languages that
> compile to YAML, such as Dhall.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FLINK-23620) Introduce proper YAML parsing to Flink's configuration
[
https://issues.apache.org/jira/browse/FLINK-23620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-23620:
---
Labels: pull-request-available stale-assigned (was: 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 issue is assigned but has not
received an update in 30 days, so it has been labeled "stale-assigned".
If you are still working on the issue, please remove the label and add a
comment updating the community on your progress. If this issue is waiting on
feedback, please consider this a reminder to the committer/reviewer. Flink is a
very active project, and so we appreciate your patience.
If you are no longer working on the issue, please unassign yourself so someone
else may work on it.
> Introduce proper YAML parsing to Flink's configuration
> --
>
> Key: FLINK-23620
> URL: https://issues.apache.org/jira/browse/FLINK-23620
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Configuration
>Reporter: Mika Naylor
>Assignee: Mika Naylor
>Priority: Minor
> Labels: pull-request-available, stale-assigned
>
> At the moment, the YAML parsing for Flink's configuration file
> ({{conf/flink-conf.yaml)}} is pretty basic. It only supports basic key value
> pairs, such as:
> {code:java}
> a.b.c: a value
> a.b.d: another value{code}
> As well as supporting some invalid YAML syntax, such as:
> {code:java}
> a: b: value{code}
>
> Introducing proper YAML parsing to the configuration component would let
> Flink users use features such as nested keys, such as:
> {code:java}
> a:
> b:
> c: a value
> d: another value{code}
> as well as make it easier to integrate configuration tools/languages that
> compile to YAML, such as Dhall.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (FLINK-23620) Introduce proper YAML parsing to Flink's configuration
[
https://issues.apache.org/jira/browse/FLINK-23620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated FLINK-23620:
---
Labels: pull-request-available (was: )
> Introduce proper YAML parsing to Flink's configuration
> --
>
> Key: FLINK-23620
> URL: https://issues.apache.org/jira/browse/FLINK-23620
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Configuration
>Reporter: Mika Naylor
>Assignee: Mika Naylor
>Priority: Minor
> Labels: pull-request-available
>
> At the moment, the YAML parsing for Flink's configuration file
> ({{conf/flink-conf.yaml)}} is pretty basic. It only supports basic key value
> pairs, such as:
> {code:java}
> a.b.c: a value
> a.b.d: another value{code}
> As well as supporting some invalid YAML syntax, such as:
> {code:java}
> a: b: value{code}
>
> Introducing proper YAML parsing to the configuration component would let
> Flink users use features such as nested keys, such as:
> {code:java}
> a:
> b:
> c: a value
> d: another value{code}
> as well as make it easier to integrate configuration tools/languages that
> compile to YAML, such as Dhall.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (FLINK-23620) Introduce proper YAML parsing to Flink's configuration
[
https://issues.apache.org/jira/browse/FLINK-23620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mika Naylor updated FLINK-23620:
Description:
At the moment, the YAML parsing for Flink's configuration file
({{conf/flink-conf.yaml)}} is pretty basic. It only supports basic key value
pairs, such as:
{code:java}
a.b.c: a value
a.b.d: another value{code}
As well as supporting some invalid YAML syntax, such as:
{code:java}
a: b: value{code}
Introducing proper YAML parsing to the configuration component would let Flink
users use features such as nested keys, such as:
{code:java}
a:
b:
c: a value
d: another value{code}
as well as make it easier to integrate configuration tools/languages that
compile to YAML, such as Dhall.
was:
At the moment, the YAML parsing for Flink's configuration file
({{conf/flink-conf.yaml)}} is pretty basic. It only supports basic key value
pairs, such as:
{code:java}
a.b.c: a value
a.b.d: another value{code}
As well as supporting some invalid YAML syntax, such as:
{code:java}
a: b: value{code}
Introducing proper YAML parsing to the configuration component would let Flink
users use features such as nested keys, such as:
{code:java}
a:
b:
c: a value
d: another value{code}
as well as make it easier to integrate configuration tools/languages that
compile to YAML, such as Dhall.
> Introduce proper YAML parsing to Flink's configuration
> --
>
> Key: FLINK-23620
> URL: https://issues.apache.org/jira/browse/FLINK-23620
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Configuration
>Reporter: Mika Naylor
>Priority: Minor
>
> At the moment, the YAML parsing for Flink's configuration file
> ({{conf/flink-conf.yaml)}} is pretty basic. It only supports basic key value
> pairs, such as:
> {code:java}
> a.b.c: a value
> a.b.d: another value{code}
> As well as supporting some invalid YAML syntax, such as:
> {code:java}
> a: b: value{code}
>
> Introducing proper YAML parsing to the configuration component would let
> Flink users use features such as nested keys, such as:
> {code:java}
> a:
> b:
> c: a value
> d: another value{code}
> as well as make it easier to integrate configuration tools/languages that
> compile to YAML, such as Dhall.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (FLINK-23620) Introduce proper YAML parsing to Flink's configuration
[
https://issues.apache.org/jira/browse/FLINK-23620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mika Naylor updated FLINK-23620:
Description:
At the moment, the YAML parsing for Flink's configuration file
(`conf/flink-conf.yaml`) is pretty basic. It only supports basic key value
pairs, such as:
{{}}
{code:java}
a.b.c: a value
a.b.d: another value{code}
As well as supporting some invalid YAML syntax, such as:
{code:java}
a: b: value{code}
Introducing proper YAML parsing to the configuration component would let Flink
users use features such as nested keys, such as:
{code:java}
a:
b:
c: a value
d: another value{code}
as well as make it easier to integrate configuration tools/languages that
compile to YAML, such as Dhall.
was:
At the moment, the YAML parsing for Flink's configuration file
(`conf/flink-conf.yaml`) is pretty basic. It only supports basic key value
pairs, such as:
```
a.b.c: a value
a.b.d: another value
```
As well as supporting some invalid YAML syntax, such as:
```
a: b: value
```
Introducing proper YAML parsing to the configuration component would let Flink
users use features such as nested keys, such as:
```
a:
b:
c: a value
d: another value
```
as well as make it easier to integrate configuration tools/languages that
compile to YAML, such as Dhall.
> Introduce proper YAML parsing to Flink's configuration
> --
>
> Key: FLINK-23620
> URL: https://issues.apache.org/jira/browse/FLINK-23620
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Configuration
>Reporter: Mika Naylor
>Priority: Minor
>
> At the moment, the YAML parsing for Flink's configuration file
> (`conf/flink-conf.yaml`) is pretty basic. It only supports basic key value
> pairs, such as:
> {{}}
> {code:java}
> a.b.c: a value
> a.b.d: another value{code}
> As well as supporting some invalid YAML syntax, such as:
> {code:java}
> a: b: value{code}
>
> Introducing proper YAML parsing to the configuration component would let
> Flink users use features such as nested keys, such as:
> {code:java}
> a:
> b:
> c: a value
> d: another value{code}
> as well as make it easier to integrate configuration tools/languages that
> compile to YAML, such as Dhall.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (FLINK-23620) Introduce proper YAML parsing to Flink's configuration
[
https://issues.apache.org/jira/browse/FLINK-23620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mika Naylor updated FLINK-23620:
Description:
At the moment, the YAML parsing for Flink's configuration file
({{conf/flink-conf.yaml)}} is pretty basic. It only supports basic key value
pairs, such as:
{code:java}
a.b.c: a value
a.b.d: another value{code}
As well as supporting some invalid YAML syntax, such as:
{code:java}
a: b: value{code}
Introducing proper YAML parsing to the configuration component would let Flink
users use features such as nested keys, such as:
{code:java}
a:
b:
c: a value
d: another value{code}
as well as make it easier to integrate configuration tools/languages that
compile to YAML, such as Dhall.
was:
At the moment, the YAML parsing for Flink's configuration file
(`conf/flink-conf.yaml`) is pretty basic. It only supports basic key value
pairs, such as:
{code:java}
a.b.c: a value
a.b.d: another value{code}
As well as supporting some invalid YAML syntax, such as:
{code:java}
a: b: value{code}
Introducing proper YAML parsing to the configuration component would let Flink
users use features such as nested keys, such as:
{code:java}
a:
b:
c: a value
d: another value{code}
as well as make it easier to integrate configuration tools/languages that
compile to YAML, such as Dhall.
> Introduce proper YAML parsing to Flink's configuration
> --
>
> Key: FLINK-23620
> URL: https://issues.apache.org/jira/browse/FLINK-23620
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Configuration
>Reporter: Mika Naylor
>Priority: Minor
>
> At the moment, the YAML parsing for Flink's configuration file
> ({{conf/flink-conf.yaml)}} is pretty basic. It only supports basic key value
> pairs, such as:
> {code:java}
> a.b.c: a value
> a.b.d: another value{code}
> As well as supporting some invalid YAML syntax, such as:
> {code:java}
> a: b: value{code}
>
> Introducing proper YAML parsing to the configuration component would let
> Flink users use features such as nested keys, such as:
> {code:java}
> a:
> b:
> c: a value
> d: another value{code}
> as well as make it easier to integrate configuration tools/languages that
> compile to YAML, such as Dhall.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (FLINK-23620) Introduce proper YAML parsing to Flink's configuration
[
https://issues.apache.org/jira/browse/FLINK-23620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mika Naylor updated FLINK-23620:
Description:
At the moment, the YAML parsing for Flink's configuration file
(`conf/flink-conf.yaml`) is pretty basic. It only supports basic key value
pairs, such as:
{code:java}
a.b.c: a value
a.b.d: another value{code}
As well as supporting some invalid YAML syntax, such as:
{code:java}
a: b: value{code}
Introducing proper YAML parsing to the configuration component would let Flink
users use features such as nested keys, such as:
{code:java}
a:
b:
c: a value
d: another value{code}
as well as make it easier to integrate configuration tools/languages that
compile to YAML, such as Dhall.
was:
At the moment, the YAML parsing for Flink's configuration file
(`conf/flink-conf.yaml`) is pretty basic. It only supports basic key value
pairs, such as:
{{}}
{code:java}
a.b.c: a value
a.b.d: another value{code}
As well as supporting some invalid YAML syntax, such as:
{code:java}
a: b: value{code}
Introducing proper YAML parsing to the configuration component would let Flink
users use features such as nested keys, such as:
{code:java}
a:
b:
c: a value
d: another value{code}
as well as make it easier to integrate configuration tools/languages that
compile to YAML, such as Dhall.
> Introduce proper YAML parsing to Flink's configuration
> --
>
> Key: FLINK-23620
> URL: https://issues.apache.org/jira/browse/FLINK-23620
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Configuration
>Reporter: Mika Naylor
>Priority: Minor
>
> At the moment, the YAML parsing for Flink's configuration file
> (`conf/flink-conf.yaml`) is pretty basic. It only supports basic key value
> pairs, such as:
> {code:java}
> a.b.c: a value
> a.b.d: another value{code}
> As well as supporting some invalid YAML syntax, such as:
> {code:java}
> a: b: value{code}
>
> Introducing proper YAML parsing to the configuration component would let
> Flink users use features such as nested keys, such as:
> {code:java}
> a:
> b:
> c: a value
> d: another value{code}
> as well as make it easier to integrate configuration tools/languages that
> compile to YAML, such as Dhall.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (FLINK-23620) Introduce proper YAML parsing to Flink's configuration
[
https://issues.apache.org/jira/browse/FLINK-23620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mika Naylor updated FLINK-23620:
Description:
At the moment, the YAML parsing for Flink's configuration file
(`conf/flink-conf.yaml`) is pretty basic. It only supports basic key value
pairs, such as:
{code:java}
a.b.c: a value
a.b.d: another value{code}
As well as supporting some invalid YAML syntax, such as:
{code:java}
a: b: value{code}
Introducing proper YAML parsing to the configuration component would let Flink
users use features such as nested keys, such as:
{code:java}
a:
b:
c: a value
d: another value{code}
as well as make it easier to integrate configuration tools/languages that
compile to YAML, such as Dhall.
was:
At the moment, the YAML parsing for Flink's configuration file
(`conf/flink-conf.yaml`) is pretty basic. It only supports basic key value
pairs, such as:
{code:java}
a.b.c: a value
a.b.d: another value{code}
As well as supporting some invalid YAML syntax, such as:
{code:java}
a: b: value{code}
Introducing proper YAML parsing to the configuration component would let Flink
users use features such as nested keys, such as:
{code:java}
a:
b:
c: a value
d: another value{code}
as well as make it easier to integrate configuration tools/languages that
compile to YAML, such as Dhall.
> Introduce proper YAML parsing to Flink's configuration
> --
>
> Key: FLINK-23620
> URL: https://issues.apache.org/jira/browse/FLINK-23620
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Configuration
>Reporter: Mika Naylor
>Priority: Minor
>
> At the moment, the YAML parsing for Flink's configuration file
> (`conf/flink-conf.yaml`) is pretty basic. It only supports basic key value
> pairs, such as:
> {code:java}
> a.b.c: a value
> a.b.d: another value{code}
> As well as supporting some invalid YAML syntax, such as:
> {code:java}
> a: b: value{code}
>
> Introducing proper YAML parsing to the configuration component would let
> Flink users use features such as nested keys, such as:
> {code:java}
> a:
> b:
> c: a value
> d: another value{code}
> as well as make it easier to integrate configuration tools/languages that
> compile to YAML, such as Dhall.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
