Biju Nair created FLUME-2573:
--------------------------------
Summary: flume-ng --config parameter is not used when starting a
flume agent
Key: FLUME-2573
URL: https://issues.apache.org/jira/browse/FLUME-2573
Project: Flume
Issue Type: Bug
Components: Node
Affects Versions: v1.4.0
Environment: ubuntu 12 & Flume 1.4.0
Reporter: Biju Nair
Fix For: v1.4.1
flume-ng script accepts the parameter `conf`
(https://github.com/apache/flume/blob/trunk/bin/flume-ng#L183) to pass the
directory which stores the configuration files and adds it to the
FLUME_CLASSPATH.
But `org.apache.flume.node.Application`
(https://github.com/apache/flume/blob/trunk/flume-ng-node/src/main/java/org/apache/flume/node/Application.java#L302)
expects
configuration files passed to have an absolute path. So even if user passes
`conf` and `conf-file` option, `application` looks for the configuration file
in the directory from which it is executed. It would be good to take the `conf`
value into consideration so that users can place the config files anywhere.
Currently big-top init.d script joins the `conf` and `conf-file` values
(https://github.com/apache/flume/blob/trunk/bin/flume-ng#L183) when calling
flume-ng. The same can be done in the ` flume-ng ` script. Alternatively
the `conf ` parameter can be read in ` application ` and concatenated in the
code. The latter is a cleaner approach but will have impact on ` big-top `.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
