Description
In the flume-ng script, the '\' and 'n' characters are each being treated as delimiters instead of being treated as a newline character. This relates to the following line of code that is found in 2 places within the script:
if [[ $line =~ ^java\.library\.path=([^\n]*) ]]; then
This causes the java.library.path's value to be truncated at the first '\' or \n' character in its value.
For example:
[will@will-laptop flume-1.2.0-incubating-SNAPSHOT]$ bin/flume-ng agent -d
...results in a java.library.path of:
-Djava.library.path=:/usr/lib/hadoop/lib/:/
..but should be:
-Djava.library.path=:/usr/lib/hadoop/lib/native:/usr/lib/hadoop/lib/native:/usr/lib/hbase/bin/../lib/native/Linux-amd64-64
Note: This issue was introduced in the fix to FLUME-1248.
Attachments
Attachments
Issue Links
- is duplicated by
-
FLUME-1294 flume-ng script parses java.library.path incorrectly
- Resolved