Models

The models object allows you to query information about all models in a given job.

Arguments

When querying for models, the following arguments are available. Note that if you do not include a runId, it will default to the most recent run of the specified job:

Fetching data...

Below we show some illustrative example queries and outline the schema of this models object.

Example Queries

As we noted above, database, schema, and identifier are all optional arguments. This means that with this endpoint, you can:

• Find a specific model by providing <database>.<schema>.<identifier>
• Find all of the models in a database and/or schema by providing <database> and/or <schema>

Finding models by their database, schema, and identifier

The example query below finds a model by its unique database, schema, and identifier.

{
  models(jobId: 123, database:"analytics", schema: "analytics", identifier:"dim_customers") {
    uniqueId
  }
}

Finding models by their schema

The example query below finds all models in this schema, and their respective execution times.

{
  models(jobId: 123, schema: "analytics") {
    uniqueId
    executionTime
  }
}

Fields

Models has access to the same fields as the Model node. The difference is that Models can output a list, so instead of querying for fields for one specific model, you can query for those parameters for all models within a jobID, database, etc.

When querying for models, the following fields are available:

Fetching data...