On the Job view located on the bottom part of the design workspace, you can define Job's optional functions. This view is made of two tabs: Stats & Logs tab and Extra tab.
The Stats & Logs tab allows you to automate the use of Stats & Logs features and the Context loading feature. For more information, see How to automate the use of statistics & logs.
The Extra tab lists various options you can set to automate some features such as the context parameters use, in the Implicit Context Loading area. For more information, see How to use the features in the Extra tab.
If you have a great need of log, statistics and other measurement of your data flows, you are facing the issue of having too many log-related components loading your Job Designs. You can automate the use of tFlowMeterCatcher, tStatCatcher, tLogCatcher component functionalities without using the components in your Job via the Stats & Logs tab.
For more information regarding the Log component, see Talend Open Studio for Big Data Components Reference Guide.
The Stats & Logs panel is located on the Job tab underneath the design workspace and prevents your Jobs Designs to be overloaded by components.
This setting supersedes the log-related components with a general log configuration.
To set the Stats & Logs properties:
Click the Job tab.
Select the Stats & Logs panel to display the configuration view.
Set the relevant details depending on the output you prefer (console, file or database).
Select the relevant Catch check box according to your needs.
You can save the settings into your Project Settings by clicking the button. This way, you can access such settings via File > Edit project settings > Job settings > Stats & Logs or via the button on the toolbar.
When you use Stats & Logs functions in your Job, you can apply them to all its subjobs.
To do so, click the Apply to subjobs button in the Stats & Logs panel of the Job view and the selected stats & logs functions of the main Job will be selected for all of its subjobs.
The Extra tab offers some optional function parameters.
Select the Multithread execution check box to allow two Job executions to start at the same time.
Set the Implicit tContextLoad option parameters to avoid using the tContextLoad component on your Job and automate the use of context parameters.
Choose between File and Database as source of your context parameters and set manually the file or database access.
Set notifications (error/warning/info) for unexpected behaviors linked to context parameter setting.
For an example of loading context parameters dynamically using the Implicit Context Load feature, see Using the Implicit Context Load feature.
When you fill in Implicit tContextLoad manually, you can store these parameters in your project by clicking the Save to project settings button, and thus reuse these parameters for other components in different Jobs.
Select the Use Project Settings check box to recuperate the context parameters you have already defined in the Project Settings view.
The Implicit tContextLoad option becomes available and all fields are filled in automatically.
For more information about context parameters, see Context settings.
Click Reload from project settings to update the context parameters list with the latest context parameters from the project settings.