Job Templates

A job template combines Building Blocks into a single configuration file for your jobs. It provides instructions to the services responsible for executing your job, and ensures your app and data engines are linked together.

By default, a job template is generated when you start building a new app, which lets you focus on developing your app without worrying about the other components.

However, it is important that your app expects a certain data type and format. Hence, when developing an app, you can link it to your partitioning and assembling engines by creating a new job template.

Here's an example:

template.json

{
  "id": "my-first-template",
  "version": 1,
  "description": "A sample description",
  "app_id": "[email protected]",
  "partitioning_engine_id": "[email protected]",
  "assembling_engine_id": "[email protected]",
  "app_schema_id": "default",
  "partitioning_schema": "default",
  "assembling_schema_id": "default"
}

Job Template Fields

app_id string

Description:

The ID of an app.

Allowed values:

string

partitioning_engine_id string

Description:

The ID of a partitioning engine.

Allowed values:

string

assembling_engine_id string

Description:

The ID of an assembling engine.

Allowed values:

string