[jira] [Updated] (FLUME-2853) Allow for YAML configuration files

2017-09-08 Thread Ferenc Szabo (JIRA)

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

Ferenc Szabo updated FLUME-2853:

Fix Version/s: (was: 1.8.0)

> Allow for YAML configuration files
> --
>
> Key: FLUME-2853
> URL: https://issues.apache.org/jira/browse/FLUME-2853
> Project: Flume
>  Issue Type: Improvement
>  Components: Configuration
>Affects Versions: 1.8.0
>Reporter: Christopher White
>Priority: Minor
>  Labels: 1.9
>
> Allow for YAML formatted configuration files 
> (http://www.yaml.org/spec/1.2/spec.html).
> This provides:
> * A more condensed format than properties files
> * Less 'typo' prone for repetitive common prefixes
> * Ability to define a value once and reuse via references (see [spec - 
> Structures - Example 2.10|http://www.yaml.org/spec/1.2/spec.html#id2760395]
> For example compare the following properties file and potential YAML 
> equivalent:
> {code:title=agent.properties}
> host1.sources = source1
> host1.channels = channel1
> host1.sinks = sink1
> host1.sources.source1.type = seq
> host1.sources.source1.channels = channel1
> host1.channels.channel1.type = memory
> host1.channels.channel1.capacity = 1
> host1.sinks.sink1.type = null
> host1.sinks.sink1.channel = channel1
> {code}
> {code:title=agent.yaml}
> host1:
>   sources:
> _: source1
> source1:
>   type: seq
>   channels: channel1
>   
>   channels:
> _: channel1
> channel1:
>   type: memory
>   capacity: 1
>   
>   sinks:
> _: sink1
> sink1:
>   type: null
>   channel: channel1
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Updated] (FLUME-2853) Allow for YAML configuration files

2017-09-08 Thread Ferenc Szabo (JIRA)

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

Ferenc Szabo updated FLUME-2853:

Labels: 1.9  (was: )

> Allow for YAML configuration files
> --
>
> Key: FLUME-2853
> URL: https://issues.apache.org/jira/browse/FLUME-2853
> Project: Flume
>  Issue Type: Improvement
>  Components: Configuration
>Affects Versions: 1.8.0
>Reporter: Christopher White
>Priority: Minor
>  Labels: 1.9
>
> Allow for YAML formatted configuration files 
> (http://www.yaml.org/spec/1.2/spec.html).
> This provides:
> * A more condensed format than properties files
> * Less 'typo' prone for repetitive common prefixes
> * Ability to define a value once and reuse via references (see [spec - 
> Structures - Example 2.10|http://www.yaml.org/spec/1.2/spec.html#id2760395]
> For example compare the following properties file and potential YAML 
> equivalent:
> {code:title=agent.properties}
> host1.sources = source1
> host1.channels = channel1
> host1.sinks = sink1
> host1.sources.source1.type = seq
> host1.sources.source1.channels = channel1
> host1.channels.channel1.type = memory
> host1.channels.channel1.capacity = 1
> host1.sinks.sink1.type = null
> host1.sinks.sink1.channel = channel1
> {code}
> {code:title=agent.yaml}
> host1:
>   sources:
> _: source1
> source1:
>   type: seq
>   channels: channel1
>   
>   channels:
> _: channel1
> channel1:
>   type: memory
>   capacity: 1
>   
>   sinks:
> _: sink1
> sink1:
>   type: null
>   channel: channel1
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Updated] (FLUME-2853) Allow for YAML configuration files

2016-07-02 Thread Lior Zeno (JIRA)

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

Lior Zeno updated FLUME-2853:
-
Affects Version/s: v1.8.0
Fix Version/s: v1.8.0

> Allow for YAML configuration files
> --
>
> Key: FLUME-2853
> URL: https://issues.apache.org/jira/browse/FLUME-2853
> Project: Flume
>  Issue Type: Improvement
>  Components: Configuration
>Affects Versions: v1.8.0
>Reporter: Christopher White
>Priority: Minor
> Fix For: v1.8.0
>
>
> Allow for YAML formatted configuration files 
> (http://www.yaml.org/spec/1.2/spec.html).
> This provides:
> * A more condensed format than properties files
> * Less 'typo' prone for repetitive common prefixes
> * Ability to define a value once and reuse via references (see [spec - 
> Structures - Example 2.10|http://www.yaml.org/spec/1.2/spec.html#id2760395]
> For example compare the following properties file and potential YAML 
> equivalent:
> {code:title=agent.properties}
> host1.sources = source1
> host1.channels = channel1
> host1.sinks = sink1
> host1.sources.source1.type = seq
> host1.sources.source1.channels = channel1
> host1.channels.channel1.type = memory
> host1.channels.channel1.capacity = 1
> host1.sinks.sink1.type = null
> host1.sinks.sink1.channel = channel1
> {code}
> {code:title=agent.yaml}
> host1:
>   sources:
> _: source1
> source1:
>   type: seq
>   channels: channel1
>   
>   channels:
> _: channel1
> channel1:
>   type: memory
>   capacity: 1
>   
>   sinks:
> _: sink1
> sink1:
>   type: null
>   channel: channel1
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)