Skip to content

Commit

Permalink
Merge branch 'current' into dbeatty10-patch-3
Browse files Browse the repository at this point in the history
  • Loading branch information
matthewshaver authored Apr 1, 2024
2 parents 2e51266 + a901096 commit eaf3cbe
Show file tree
Hide file tree
Showing 15 changed files with 140 additions and 72 deletions.
10 changes: 5 additions & 5 deletions website/docs/docs/cloud/cloud-cli-installation.md
Original file line number Diff line number Diff line change
Expand Up @@ -10,11 +10,11 @@ dbt Cloud natively supports developing using a command line (CLI), empowering te

dbt commands are run against dbt Cloud's infrastructure and benefit from:

* Secure credential storage in the dbt Cloud platform.
* [Automatic deferral](/docs/cloud/about-cloud-develop-defer) of build artifacts to your Cloud project's production environment.
* Speedier, lower-cost builds.
* Support for dbt Mesh ([cross-project `ref`](/docs/collaborate/govern/project-dependencies)),
* Significant platform improvements, to be released over the coming months.
* Secure credential storage in the dbt Cloud platform
* [Automatic deferral](/docs/cloud/about-cloud-develop-defer) of build artifacts to your Cloud project's production environment
* Speedier, lower-cost builds
* Support for dbt Mesh ([cross-project `ref`](/docs/collaborate/govern/project-dependencies))
* Significant platform improvements, to be released over the coming months

<Lightbox src="/img/docs/dbt-cloud/cloud-cli-overview.jpg" title="Diagram of how the dbt Cloud CLI works with dbt Cloud's infrastructure to run dbt commands from your local command line." />

Expand Down
161 changes: 95 additions & 66 deletions website/docs/docs/collaborate/explore-projects.md

Large diffs are not rendered by default.

Original file line number Diff line number Diff line change
@@ -0,0 +1,26 @@
---
title: "dbt Semantic Layer updates and fixes for March 2024"
description: "March 2024 updates for dbt Semantic Layer & MetricFlow: New export features, enhanced date filters, Tableau, Google Sheets & GraphQL API enhancements, and bug fixes."
sidebar_label: "Updates and fixes: dbt Semantic Layer"
sidebar_position: 10
tags: [Mar-2024]
date: 2024-04-01
---

The dbt Labs team continues to work on adding new features, fixing bugs, and increasing reliability for the [dbt Semantic Layer](/docs/use-dbt-semantic-layer/dbt-sl) and [MetricFlow](/docs/build/about-metricflow). This release note includes our work in March 2024:

## New features

- **Privatelink:** The Semantic Layer services now support using Privatelink for customers who have it enabled.
- **SSO support for Semantic Layer development:** You can now develop against and test your Semantic Layer in the Cloud CLI if your developer credential uses SSO.

## Updates

**Entities are selectable in the Google Sheets app:** You can select entities to Group By, Filter By, and Order By.


## Bug fixes

- `dbt parse` no longer shows an error when you use a list of filters (instead of just a string filter) on a metric.
- `join_to_timespine` now properly gets applied to conversion metric input measures.
- Fixed an issue where exports in Redshift were not always committing to the DWH, which also had the side-effect of leaving table locks open.
1 change: 0 additions & 1 deletion website/docs/docs/deploy/deploy-jobs.md
Original file line number Diff line number Diff line change
Expand Up @@ -113,7 +113,6 @@ You can set up a configuration where an upstream job triggers multiple downstrea

For jobs that are triggered to run by another job, a link to the upstream job run is available from your [job's run details](/docs/deploy/run-visibility#job-run-details).


## Related docs

- [Artifacts](/docs/deploy/artifacts)
Expand Down
14 changes: 14 additions & 0 deletions website/docs/docs/deploy/job-scheduler.md
Original file line number Diff line number Diff line change
Expand Up @@ -29,6 +29,7 @@ Familiarize yourself with these useful terms to help you understand how the job
| Job | A collection of run steps, settings, and a trigger to invoke dbt commands against a project in the user's cloud data platform. |
| Job queue | The job queue acts as a waiting area for job runs when they are scheduled or triggered to run; runs remain in queue until execution begins. More specifically, the Scheduler checks the queue for runs that are due to execute, ensures the run is eligible to start, and then prepares an environment with appropriate settings, credentials, and commands to begin execution. Once execution begins, the run leaves the queue. |
| Over-scheduled job | A situation when a cron-scheduled job's run duration becomes longer than the frequency of the job’s schedule, resulting in a job queue that will grow faster than the scheduler can process the job’s runs. |
| Deactivated job | A situation where a job has reached 100 consecutive failing runs. |
| Prep time | The time dbt Cloud takes to create a short-lived environment to execute the job commands in the user's cloud data platform. Prep time varies most significantly at the top of the hour when the dbt Cloud Scheduler experiences a lot of run traffic. |
| Run | A single, unique execution of a dbt job. |
| Run slot | Run slots control the number of jobs that can run concurrently. Developer plans have a fixed number of run slots, while Enterprise and Team plans have [unlimited run slots](/docs/dbt-versions/release-notes/July-2023/faster-run#unlimited-job-concurrency-for-enterprise-accounts). Each running job occupies a run slot for the duration of the run. <br /><br />Team and Developer plans are limited to one project each. For additional projects, consider upgrading to the [Enterprise plan](https://www.getdbt.com/pricing/).|
Expand Down Expand Up @@ -82,6 +83,19 @@ The scheduler prevents queue clog by canceling runs that aren't needed, ensuring

To prevent over-scheduling, users will need to take action by either refactoring the job so it runs faster or modifying its [schedule](/docs/deploy/deploy-jobs#schedule-days).

## Deactivation of jobs <Lifecycle status='beta' />

To reduce unnecessary resource consumption and reduce contention for run slots in your account, dbt Cloud will deactivate a [deploy job](/docs/deploy/deploy-jobs) or a [CI job](/docs/deploy/ci-jobs) if it reaches 100 consecutive failing runs and indicate this through the use of banners. When this happens, scheduled and triggered-to-run jobs will no longer be enqueued.

To reactivate a deactivated job, you can either:
- Update the job's settings to fix the issue and save the job (recommended)
- Perform a manual run by clicking **Run now** on the job's page


Example of deactivation banner on job's page:

<Lightbox src="/img/docs/dbt-cloud/deployment/example-deactivated-deploy-job.png" title="Example of deactivation banner on job's page"/>

## Related docs
- [dbt Cloud architecture](/docs/cloud/about-cloud/architecture#dbt-cloud-features-architecture)
- [Job commands](/docs/deploy/job-commands)
Expand Down
Binary file not shown.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.

0 comments on commit eaf3cbe

Please sign in to comment.