omhdfs: Hadoop Filesystem Output Module¶
|Author:||Rainer Gerhards <email@example.com>|
This module supports writing message into files on Hadoop’s HDFS file system.
Parameter names are case-insensitive.
obsolete legacy Directives¶
The name of the file to which the output data shall be written.
Name or IP address of the HDFS host to connect to.
Port on which to connect to the HDFS host.
Default template to be used when none is specified. This saves the work of specifying the same template ever and ever again. Of course, the default template can be overwritten via the usual method.
Building omhdfs is a challenge because we could not yet find out how to integrate Java properly into the autotools build process. The issue is that HDFS is written in Java and libhdfs uses JNI to talk to it. That requires that various system-specific environment options and paths be set correctly. At this point, we leave this to the user. If someone knows how to do it better, please drop us a line!
- In order to build, you need to set these environment variables BEFORE
- JAVA_INCLUDES - must have all include paths that are needed to build JNI C programs, including the -I options necessary for gcc. An example is # export JAVA_INCLUDES=”-I/usr/lib/jvm/java-1.6.0-openjdk-22.214.171.124.x86_64/include -I/usr/lib/jvm/java-1.6.0-openjdk-126.96.36.199.x86_64/include/linux”
- JAVA_LIBS - must have all library paths that are needed to build JNI C programs, including the -l/-L options necessary for gcc. An example is # export export JAVA_LIBS=”-L/usr/java/jdk1.6.0_21/jre/lib/amd64 -L/usr/java/jdk1.6.0_21/jre/lib/amd64/server -ljava -ljvm -lverify”
- As of HDFS architecture, you must make sure that all relevant environment variables (the usual Java stuff and HADOOP’s home directory) are properly set.
- As it looks, libhdfs makes Java throw exceptions to stdout. There is no known work-around for this (and it usually should not case any troubles.
$ModLoad omhdfs $OMHDFSFileName /var/log/logfile \*.\* :omhdfs:
Help with configuring/using