Setting up code dependencies on a Job - Cloud - 8.0

Talend Studio User Guide

Version
Cloud
8.0
Language
English
Product
Talend Big Data
Talend Big Data Platform
Talend Cloud
Talend Data Fabric
Talend Data Integration
Talend Data Management Platform
Talend Data Services Platform
Talend ESB
Talend MDM Platform
Talend Real-Time Big Data Platform
Module
Talend Studio
Content
Design and Development
Last publication date
2024-02-29

If you want to enable your Job to call any function in a routine or custom routine jar, you need to set up code dependencies, namely routine or custom routine jar dependencies, on the Job.

For more information about routines and custom routine jars, see What are routines and Creating custom routine JARs.

Procedure

  1. Right-click your Job and select Setup Codes Dependencies from the contextual menu in the Repository tree view. Otherwise, select Setup routine dependencies.
    A dialog box with two tabs Custom Routine Jars and Global routines is displayed. You can set up custom routine jar and global routine dependencies on the Job on the corresponding tab. By default, all system routines are automatically set as dependencies for Jobs.
    Setup Codes Dependencies dialog box.
  2. Click the [+] button on a tab if you need to set up the corresponding dependencies on the Job.
    A dialog box is displayed, which lists all the corresponding routines or custom routines jars.
  3. Select one or more routines or custom routine jars containing the functions that your Job calls.
  4. Click OK to save your changes and close the dialog box.

    If a routine or a custom routine jar does not contain any function that your Job calls, you can remove it by selecting it on the tab and then clicking the [x] button. This will help avoid redundancy in the exported dependencies.

    Note: You can right-click a routine or a custom routine jar to use the Impact Analysis feature. This feature indicates which Jobs use the routine or the custom routine jar and would therefore be impacted by any modification. For further information about Impact Analysis, see Analyzing repository items.