It is quite unlikely for client code to make a CodecPailStructure CodecPailStructure is constructed by PailSource's factory methods.
A tsv source with the column name header info.
A tsv source with the column name header info.
Header file format: tab separated column names.
Source used to write some type T into an LZO-compressed SequenceFile using a codec on T for serialization.
The PailSource enables scalding integration with the Pail class in the dfs-datastores library.
The PailSource enables scalding integration with the Pail class in the dfs-datastores library. PailSource allows scalding to sink 1-tuples to subdirectories of a root folder by applying a routing function to each tuple.
SEE EXAMPLE : https://gist.github.com/krishnanraman/5224937
Source used to write key-value pairs as byte arrays into a versioned store.
Source used to write key-value pairs as byte arrays into a versioned store. Supports incremental updates via the monoid on V.
It is quite unlikely for client code to make a CodecPailStructure CodecPailStructure is constructed by PailSource's factory methods.
targetFn takes an instance of T and returns a list "path components". Pail joins these components with File.separator and sinks the instance of T into the pail at that location.
Usual implementations of "validator" will check that the length of the supplied list is >= the length f the list returned by targetFn.
CodecPailStructure has a default constructor because it is instantiated via reflection This unfortunately means params must be set via setParams to make it usefuls