A path to use for the local tap.
A path to use for the local tap.
Creates a local tap.
Creates a local tap.
The mode for handling output conflicts.
Subclasses of Source MUST override this method.
Subclasses of Source MUST override this method. They may call out to TestTapFactory for making Taps suitable for testing.
The scheme to use if the source is on hdfs.
The scheme to use if the source is on hdfs.
The scheme to use if the source is local.
The scheme to use if the source is local.
Determines if a path is 'valid' for this source.
Determines if a path is 'valid' for this source. In strict mode all paths must be valid. In non-strict mode, all invalid paths will be filtered out.
Subclasses can override this to validate paths.
The default implementation is a quick sanity check to look for missing or empty directories. It is necessary but not sufficient -- there are cases where this will return true but there is in fact missing data.
TODO: consider writing a more in-depth version of this method in TimePathedSource that looks for TODO: missing days / hours etc.
This is a name the refers to this exact instance of the source (put another way, if s1.sourceId == s2.sourceId, the job should work the same if one is replaced with the other
This is a name the refers to this exact instance of the source (put another way, if s1.sourceId == s2.sourceId, the job should work the same if one is replaced with the other
The mock passed in to scalding.JobTest may be considered as a mock of the Tap or the Source.
The mock passed in to scalding.JobTest may be considered as a mock of the Tap or the Source. By default, as of 0.9.0, it is considered as a Mock of the Source. If you set this to true, the mock in TestMode will be considered to be a mock of the Tap (which must be transformed) and not the Source.
write the pipe but return the input so it can be chained into the next operation
write the pipe but return the input so it can be chained into the next operation
(Since version 0.9.0) replace with Mappable.toIterator
Ensures that a _SUCCESS file is present in every directory included by a glob, as well as the requirements of FileSource.pathIsGood. The set of directories to check for _SUCCESS is determined by examining the list of all paths returned by globPaths and adding parent directories of the non-hidden files encountered. pathIsGood should still be considered just a best-effort test. As an illustration the following layout with an in-flight job is accepted for the glob dir*/*:
Similarly if dir1 is physically empty pathIsGood is still true for dir*/* above
On the other hand it will reject an empty output directory of a finished job: