[
https://issues.apache.org/jira/browse/FLUME-1941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13603986#comment-13603986
]
Mike Percy commented on FLUME-1941:
-----------------------------------
I don't think bash interprets double curly brackets:
{noformat}
$ echo $0
-bash
$ ls {{k}}
ls: {{k}}: No such file or directory
{noformat}
This {{parent}} concept is quite similar to the {{\_\_prototype\_\_}} concept
in the above proposal. Restricting it to only allowing inheriting from the same
type (for some definition of type) makes a lot of sense.
> Support defaults or inheritance in configs
> ------------------------------------------
>
> Key: FLUME-1941
> URL: https://issues.apache.org/jira/browse/FLUME-1941
> Project: Flume
> Issue Type: New Feature
> Components: Configuration
> Reporter: Mike Percy
> Fix For: v1.4.0
>
>
> Proposal to support defaults or inheritance in configs.
> The idea is to create a "prototypal" component config, such as a source or
> sink, which is not necessarily instantiated but is used to avoid repetitive
> configurations when creating multiple components of the same type. A great
> example of this is users who define 5 HDFS sinks to increase write
> parallelism, but they each contain many of the same configuration parameters
> and differ only in their name and path.
> Basic idea:
> {noformat}
> agent.sinks.sink-proto-1.type = my-sink
> agent.sinks.sink-proto-1.path = /var/log/foo/bar
> agent.sinks.sink-proto-1.serializer = MySerializer$Builder
> agent.sinks.sink-proto-1.credentials = mpercy
> agent.sinks.sink-1.__prototype__ = sink-proto-1
> agent.sinks.sink-1.path = /var/log/baz/blam
> agent.sinks.sink-2.__prototype__ = sink-proto-1
> agent.sinks.sink-2.path = /var/log/glerp/bazinga
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
