Team Studio Operator Job Names
The following is a list of Team Studio job names that can be referenced for overriding specific Hadoop MapReduce data source parameters only for particular operator tasks.
Note: Workflow variables created to reference these values apply to MapReduce jobs only, not to Pig, Spark, or Sqoop jobs.
- SummarizerJob
- PCAJob
- PCA_Q_Job
- PCA_Bt_Job
- PCA_Iter_ABt_Job
- PCA_Generating_PCs_Job
- Convert_Input_Data_to_ Compressed_Sequence_File
- SVM_Prediction
- TimeSeries_Sort
- DecisionTree_Depth
- DecisionTree_Parse_Splits
- Goodness_Of_Fit
- Kmeans_Post
- Kmeans_Init
- Hadoop_Union
- Hadoop_Join
- Hadoop_Distinct
- Hadoop_Join_preProcess
- Kmeans_Iteration
- Kmeans_Output
- Max_Min_Job
- Lift_DataGenerator
- LinearRegression_Predictor
- LinearRegression
- LinearRegression_QQ
- LinearRegression_Statistics
- LinearRegression_Beta
- FeatureExtractor
- LogisticRegression_Iterator
- logisticRegression_One_Pass
- ROC_DataGenerator
- Distinct_Job
- VariableSelection_ AlphaBetaCoefficients
- VariableSelection_R2
- NaiveBayes
- ConfusionMatrix
- NaiveBayesVisualization
- NaiveBayesInitialJobForSparseData
- InformationGainVariableSelection
- Alpine_Forest_InMemory
- pivot
- ForestOOB
- Collapse
- PCA_Apply
- Correlation
- Classifier_Predictor
Determining Operator Job Names
Each operator's job name can be seen in the Results window while a workflow is running. These are the job names that can be referred to for variable settings overrides for Hadoop data source connections.
The following example displays the Results window for a K-Means workflow running various Hadoop MapReduce jobs (AlpineKmeans_init, AlpineKmeans_Iteration, AlpineKmeans_Output, and AlpineKmeans_Post).
Related concepts
Related tasks
Copyright © Cloud Software Group, Inc. All rights reserved.