[FLUME-1303] java.library.path value is being truncated at first 'n' char

• Type: Bug
• Status: Resolved
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 1.2.0
• Fix Version/s: 1.2.0
• Component/s: Shell

Environment

RHEL 6.2 64-bit

• Assignee: Will McQueen
• Reporter: Will McQueen
• Created: 21/Jun/12 12:09
• Updated: 21/Jun/12 19:49
• Resolved: 21/Jun/12 18:28

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.

Issue Links

• is duplicated by: FLUME-1294 flume-ng script parses java.library.path incorrectly