Getting Started

Writing to HDFS

The samza-hdfs module implements a Samza Producer to write to HDFS. The current implementation includes a ready-to-use HdfsSystemProducer, and three HdfsWriters: One that writes messages of raw bytes to a SequenceFile of BytesWritable keys and values. Another writes UTF-8 Strings to a SequenceFile with LongWritable keys and Text values. The last one writes out Avro data files including the schema automatically reflected from the POJO objects fed to it.

Configuring an HdfsSystemProducer

You can configure an HdfsSystemProducer like any other Samza system: using configuration keys and values set in a file. You might configure the system producer for use by your StreamTasks like this:

# set the SystemFactory implementation to instantiate HdfsSystemProducer aliased to 'hdfs-clickstream'

# define a serializer/deserializer for the hdfs-clickstream system
# DO NOT define (i.e. comment out) a SerDe when using the AvroDataFileHdfsWriter so it can reflect the schema

# consumer configs not needed for HDFS system, reader is not implemented yet

# Assign a Metrics implementation via a label we defined earlier in the props file

# Assign the implementation class for this system's HdfsWriter

# Set compression type supported by chosen Writer. Only BLOCK compression is supported currently
# AvroDataFileHdfsWriter supports snappy, bzip2, deflate or none (null, anything other than the first three)

# The base dir for HDFS output. The default Bucketer for SequenceFile HdfsWriters
# is currently /BASE/JOB_NAME/DATE_PATH/FILES, where BASE is set below

# Assign the implementation class for the HdfsWriter's Bucketer

# Configure the DATE_PATH the Bucketer will set to bucket output files by day for this job run.

# Optionally set the max output bytes (records for AvroDataFileHdfsWriter) per file.
# A new file will be cut and output continued on the next write call each time this many bytes
# (records for AvroDataFileHdfsWriter) are written.

The above configuration assumes a Metrics and Serde implemnetation has been properly configured against the some-serde-impl and some-metrics-impl labels somewhere else in the same file. Each of these properties has a reasonable default, so you can leave out the ones you don’t need to customize for your job run.