This is an automatically generated e-mail. To reply, visit:
(Updated April 15, 2014, 10:38 p.m.)
Review request for Flume.
updating patch. simplifying classpath construction in startup script as too long classpath is sometimes leading the command line length to exceed windows shell limits.
Flume startup script for windows.
The command line options have slightly changed (form unix script) to accomodate powershell requirements:
- cannot have case sensitive options: -d (dry run) and -D (java props). Similary -C & -c.
- double hyphen is not allowed. So instead of --option, we use -option
- multiple options with same name are not allowed. So instead of -classpath a=1 -classpath b=2 .. will change to -classpath "a=1;b=2"
Usage: flume-ng <command> [options]...
help display this help text
agent run a Flume agent
avro-client run an avro Flume client
version show Flume version info
-conf <conf> use configs in <conf> directory
-classpath,-C ""value1;value2; .."" append to the classpath
-property ""name1=val;name2=val; .."" sets a JDK system property value
-dryrun,-d do not actually start Flume (test)
-conf-file,-f <file> specify a config file (required)
-name,-n <name> the name of this agent (required)
-host,-H <host> hostname to which events will be sent (required)
-port,-p <port> port of the avro source (required)
-filename <file> text file to stream to avro source [default: std input]
-headerFile,-R <file> headerFile containing headers as key/value pairs on each new line