2. Command Settings

After configuring Schedule Settings of a Bolt Schedule, you’ll specify the commands you want the schedule to execute. Command Settings allow you to define which commands run when the schedule is triggered, supporting a variety of workflows, including dbt and Elementary Data commands.

Overview

With Command Settings, you can:

  • Select commands (dbt, Elementary Data, and others) to run in Paradime

  • Set the order of command execution

  • Customize options for each command

  • Create custom command combinations to suit your workflows


Available Commands

Paradime Bolt currently supports dbt and Elementary Data commands, with more to be added soon.

Supported Commands:

  1. dbt Commands: Paradime runs common dbt commands, such as dbt run, dbt est, dbt seed, dbt snapshot, and dbt build. Each command can be customized with flags to fit your CI/CD or production needs.

  2. Elementary Data Commands: Elementary provides data observability, allowing you to run anomaly detection tests, schema tests, and track data quality across your dbt models.

For new Elementary users, visit the Elementary Data Documentation for installation and configuration steps in Paradime.


How to Write and Configure Commands

  1. Basic Commands: Specify the primary command, such as dbt run or edr monitor, to perform data transformations or observability checks.

  2. Multiple commands: you can have one ore more commands in an given schedule, by simply define the commands each in a separate line, for example:

dbt seed
dbt run --select +orders
dbt test
  1. Use of target to point to different data warehouse connections:

  • Default Connection: Paradime uses the Scheduler Environment default connection for executing runs.

  • Alternative Connections: To use a different connection in your Scheduler Environment, apply the --target flag to specify an alternative connection, such as staging or ci (e.g., dbt run --target ci).


Command Best Practices

  1. Optimize Execution: Use selective commands like dbt run --select for faster builds, targeting only the required models in your pipeline

  2. Command Order: Follow a structured execution order:

    • Start with dbt seed for reference data

    • Run models, tests

    • Execute Elementary at the end of your pipeline to have more granular alerts on your dbt project.


Now, let's learn how to configure the Trigger Types of a Bolt Schedule.

Last updated

Was this helpful?

#350: Bolt - Template fixes pt 1

Change request updated