You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flume.apache.org by "E. Sammer (Updated) (JIRA)" <ji...@apache.org> on 2011/10/22 23:22:32 UTC
[jira] [Updated] (FLUME-625) new lines in flume-site.xml within
break the configuration of flume.plugin.classes
[ https://issues.apache.org/jira/browse/FLUME-625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
E. Sammer updated FLUME-625:
----------------------------
Assignee: (was: E. Sammer)
Status: Open (was: Patch Available)
Canceling patch available status due to a lack of ICLA / CCLA and removing myself from the assignee. Not going to have time to focus on it.
> new lines in flume-site.xml within break the configuration of flume.plugin.classes
> ----------------------------------------------------------------------------------
>
> Key: FLUME-625
> URL: https://issues.apache.org/jira/browse/FLUME-625
> Project: Flume
> Issue Type: Improvement
> Affects Versions: v0.9.3
> Environment: Linux, OSX
> Reporter: Disabled imported user
> Labels: configuration, flume-site.xml, flume.plugin.classes, property
>
> When specifying multiple classes in property flume.plugin.classes in flume-site.xml and there is a line break at the end (which easily happens if for example the eclipse XML formatter formats the config file), the class can not be found by flume:
> e.g.:
> <property>
> <name>flume.plugin.classes</name>
> <value>com.bla.Something,com.bla.Something2
> </value>
> <description>Comma separated list of plugin classes</description>
> </property>
> This results in a ClassNotFoundException for com.bla.Something2 when starting flume.
> At least the beginning and end of the property value should be trimmed. Even better would be, if it were possible to also have newlines allowed after the commata, so the config value can be formatted, which would ease the process of plugin management when having lots of plugins.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira