Context for running examples on the cluster
trait for creating contexts having ScoobiConfigurations
Context for running examples in memory
Context for running examples locally
Context for showing that an execution is skipped
the categories to show when logging, as a regular expression
a context chaining a sequence of contexts
the classes directories to include on a job classpath
cleanup temporary files after job execution
cleanup temporary files after job execution
context for cluster execution
context for cluster execution
a configuration object set with the properties found in the hadoop directories
set command-line arguments on the configuration object
set command-line arguments on the configuration object
a configuration with cluster setup
a configuration with memory setup
a configuration with local setup
a configuration where the appropriate properties are set-up for uploaded jars: distributed files + classpath
define the context to use: local, cluster, localThenCluster
define the context to use: local, cluster, localThenCluster
all contexts to run
all contexts to run
delete the remote jars currently on the cluster
true if the libjars must be deleted before the Scoobi job runs
the execution time will not be displayed with this function, but by adding more information to the execution Result
the execution time will not be displayed with this function, but by adding more information to the execution Result
a function to display execution times. The default uses log messages
execute some code locally
execute some code locally
execute some code on the cluster, setting the filesystem / jobtracker addresses and setting up the classpath
execute some code on the cluster, setting the filesystem / jobtracker addresses and setting up the classpath
execute some code locally
execute some code locally
make the context available implicitly as an Fixture[ScoobiConfiguration] so that examples taking that context as a parameter can be declared
make the context available implicitly as an Fixture[ScoobiConfiguration] so that examples taking that context as a parameter can be declared
the framework name: yarn, classic or local. This is only relevant for CDH5
the filesystem address
execute an example body locally
execute an example body locally
context for in memory execution
context for in memory execution
execute some code in memory, using a collection backend, possibly showing execution times
execute some code in memory, using a collection backend, possibly showing execution times
true if you want to include the library jars in the jar that is sent to the cluster for each job
true if the cluster argument is specified and the local argument is not
true if there are some configuration directories for hadoop
tests are always in memory by default, unless !inmemory is passed
tests are always in memory by default, unless !inmemory is passed
tests are always local by default, unless !local is passed
tests are always local by default, unless !local is passed
alias for locally
alias for locally
the list of library jars to upload
the jobtracker address
false if temporary files and working directory must be cleaned-up after job execution
the log level to use when logging
the path of the directory to use when loading jars to the filesystem.
context for local execution
context for local execution
execute an example body locally
execute an example body locally
true if the Scoobi job must be run locally
false if libjars are used
execute some code on the cluster, possibly showing the execution time
execute some code on the cluster, possibly showing the execution time
execute some code, either locally or on the cluster, depending on the local argument being passed on the commandline
execute some code, either locally or on the cluster, depending on the local argument being passed on the commandline
execute some code locally, possibly showing execution times
execute some code locally, possibly showing execution times
for testing, the output must be quiet by default, unless verbose is specified
for testing, the output must be quiet by default, unless verbose is specified
true to suppress log messages
execute an example body on the cluster
execute an example body on the cluster
the result of the in-memory run
the cluster evaluation of t
the result of the local run
the scoobi arguments passed on the command line
the scoobi arguments passed on the command line
set the default configuration, depending on the arguments
set the default configuration, depending on the arguments
Static setup to use a testing log factory
Static setup to use a testing log factory
true if the debug logs must show the computation graph and not evaluate it
measure the time taken by some executed code and display the time with a specific display function
measure the time taken by some executed code and display the time with a specific display function
true to display execution times for each job
context for showing a skipped execution
context for showing a skipped execution
this variable controls if the upload must be done at all
this variable controls if the upload must be done at all
upload the jars which don't exist yet in the library directory on the cluster
upload the jars which don't exist yet in the library directory on the cluster
create a Step to upload the jars on the cluster
create a Step to upload the jars on the cluster
the remote jars currently on the cluster
true if cluster configuration must be loaded from Hadoop's configuration directory
the time for the execution of a piece of code
Hadoop specification with an acceptance specification