Database Reference
In-Depth Information
%
echo "Hello Flume" > /tmp/spooldir/.file1.txt
%
mv /tmp/spooldir/.file1.txt /tmp/spooldir/file1.txt
Back in the agent's terminal, we see that Flume has detected and processed the file:
Preparing to move file /tmp/spooldir/file1.txt to
/tmp/spooldir/file1.txt.COMPLETED
Event: { headers:{} body: 48 65 6C 6C 6F 20 46 6C 75 6D 65
Hello Flume }
The spooling directory source ingests the file by splitting it into lines and creating a Flume
event for each line. Events have optional headers and a binary body, which is the UTF-8
representation of the line of text. The body is logged by the logger sink in both hexa-
decimal and string form. The file we placed in the spooling directory was only one line
long, so only one event was logged in this case. We also see that the file was renamed to
file1.txt.COMPLETED
by the source, which indicates that Flume has completed process-
ing it and won't process it again.
