Skip to content

Commit

Permalink
Updating links
Browse files Browse the repository at this point in the history
  • Loading branch information
matthewshaver committed Jul 16, 2024
1 parent b9de339 commit 4b8965a
Show file tree
Hide file tree
Showing 5 changed files with 9 additions and 9 deletions.
2 changes: 1 addition & 1 deletion website/blog/2022-08-31-august-product-update.md
Original file line number Diff line number Diff line change
Expand Up @@ -22,7 +22,7 @@ You’ll hear more in [Tristan’s keynote](https://coalesce.getdbt.com/agenda/k

## **What's new**

- **dbt Core v1.3 beta:** Do you use Python for analytics? The first beta prerelease of dbt Core v1.3—including support for dbt models written in Python—is [ready to explore](https://docs.getdbt.com/docs/dbt-versions/core-upgrade/older-versions/upgrading-to-v1.3)! Check it out, and read more about dbt supported Python models [in our docs](/docs/build/python-models).
- **dbt Core v1.3 beta:** Do you use Python for analytics? The first beta prerelease of dbt Core v1.3—including support for dbt models written in Python—is [ready to explore](https://docs.getdbt.com/docs/dbt-versions/core-upgrade/older%20versions/upgrading-to-v1.3)! Check it out, and read more about dbt supported Python models [in our docs](/docs/build/python-models).
- **Technology Partner Program:** We just launched our new [Technology Partner Program](https://www.getdbt.com/blog/dbt-labs-technology-partner-program/) with 40+ friends in the Modern Data Stack to provide consistent support for seamless integrations joint-users can trust. Check our new [dbt Cloud integrations page](http://www.getdbt.com/product/integrations) for what’s available today!
- **Single-tenant users:** dbt Cloud v1.1.60 is now available on dbt Cloud Enterprise.

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -120,7 +120,7 @@ clean-targets:
- Do you have custom scripts that parse dbt <Term id="json" /> artifacts?
- (BigQuery only) Do you use dbt's legacy capabilities around ingestion-time-partitioned tables?

If you believe your project might be affected, read more details in the migration guide [here](/docs/dbt-versions/core-upgrade/older-versions/upgrading-to-v1.0).
If you believe your project might be affected, read more details in the migration guide [here](/docs/dbt-versions/core-upgrade/older%20versions/upgrading-to-v1.0).

</details>

Expand Down
2 changes: 1 addition & 1 deletion website/docs/guides/dbt-python-snowpark.md
Original file line number Diff line number Diff line change
Expand Up @@ -395,7 +395,7 @@ In this step, we’ll need to create a development branch and set up project lev
- `materialized` &mdash; Tells dbt how to materialize models when compiling the code before it pushes it down to Snowflake. All models in the `marts` folder will be built as tables.
- `tags` &mdash; Applies tags at a directory level to all models. All models in the `aggregates` folder will be tagged as `bi` (abbreviation for business intelligence).
- `docs` &mdash; Specifies the `node_color` either by the plain color name or a hex value.
5. [Materializations](/docs/build/materializations) are strategies for persisting dbt models in a warehouse, with `tables` and `views` being the most commonly utilized types. By default, all dbt models are materialized as views and other materialization types can be configured in the `dbt_project.yml` file or in a model itself. It’s very important to note *Python models can only be materialized as tables or incremental models.* Since all our Python models exist under `marts`, the following portion of our `dbt_project.yml` ensures no errors will occur when we run our Python models. Starting with [dbt version 1.4](/docs/dbt-versions/core-upgrade/older-versions/upgrading-to-v1.4#updates-to-python-models), Python files will automatically get materialized as tables even if not explicitly specified.
5. [Materializations](/docs/build/materializations) are strategies for persisting dbt models in a warehouse, with `tables` and `views` being the most commonly utilized types. By default, all dbt models are materialized as views and other materialization types can be configured in the `dbt_project.yml` file or in a model itself. It’s very important to note *Python models can only be materialized as tables or incremental models.* Since all our Python models exist under `marts`, the following portion of our `dbt_project.yml` ensures no errors will occur when we run our Python models. Starting with [dbt version 1.4](/docs/dbt-versions/core-upgrade/older%20versions/upgrading-to-v1.4#updates-to-python-models), Python files will automatically get materialized as tables even if not explicitly specified.
```yaml
marts:    
Expand Down
2 changes: 1 addition & 1 deletion website/docs/guides/migrate-from-spark-to-databricks.md
Original file line number Diff line number Diff line change
Expand Up @@ -20,7 +20,7 @@ You can migrate your projects from using the `dbt-spark` adapter to using the [d

### Prerequisites

- Your project must be compatible with dbt 1.0 or greater. Refer to [Upgrading to v1.0](/docs/dbt-versions/core-upgrade/older-versions/upgrading-to-v1.0) for details. For the latest version of dbt, refer to [Upgrading to v1.7](/docs/dbt-versions/core-upgrade/upgrading-to-v1.7).
- Your project must be compatible with dbt 1.0 or greater. Refer to [Upgrading to v1.0](/docs/dbt-versions/core-upgrade/older%20versions/upgrading-to-v1.0) for details. For the latest version of dbt, refer to [Upgrading to v1.7](/docs/dbt-versions/core-upgrade/upgrading-to-v1.7).
- For dbt Cloud, you need administrative (admin) privileges to migrate dbt projects.

### Simpler authentication
Expand Down
10 changes: 5 additions & 5 deletions website/snippets/core-versions-table.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,11 +6,11 @@
| [**v1.7**](/docs/dbt-versions/core-upgrade/upgrading-to-v1.7) | Nov 2, 2023 | Critical &mdash; Nov 1, 2024 |
| [**v1.6**](/docs/dbt-versions/core-upgrade/upgrading-to-v1.6) | Jul 31, 2023 | Critical &mdash; Jul 30, 2024 |
| [**v1.5**](/docs/dbt-versions/core-upgrade/upgrading-to-v1.5) | Apr 27, 2023 | End of Life* ⚠️ |
| [**v1.4**](/docs/dbt-versions/core-upgrade/older-versions/upgrading-to-v1.4) | Jan 25, 2023 | End of Life* ⚠️ |
| [**v1.3**](/docs/dbt-versions/core-upgrade/older-versions/upgrading-to-v1.3) | Oct 12, 2022 | End of Life* ⚠️ |
| [**v1.2**](/docs/dbt-versions/core-upgrade/older-versions/upgrading-to-v1.2) | Jul 26, 2022 | End of Life* ⚠️ |
| [**v1.1**](/docs/dbt-versions/core-upgrade/older-versions/upgrading-to-v1.1) | Apr 28, 2022 | End of Life* ⚠️ |
| [**v1.0**](/docs/dbt-versions/core-upgrade/older-versions/upgrading-to-v1.0) | Dec 3, 2021 | End of Life* ⚠️ |
| [**v1.4**](/docs/dbt-versions/core-upgrade/older%20versions/upgrading-to-v1.4) | Jan 25, 2023 | End of Life* ⚠️ |
| [**v1.3**](/docs/dbt-versions/core-upgrade/older%20versions/upgrading-to-v1.3) | Oct 12, 2022 | End of Life* ⚠️ |
| [**v1.2**](/docs/dbt-versions/core-upgrade/older%20versions/upgrading-to-v1.2) | Jul 26, 2022 | End of Life* ⚠️ |
| [**v1.1**](/docs/dbt-versions/core-upgrade/older%20versions/upgrading-to-v1.1) | Apr 28, 2022 | End of Life* ⚠️ |
| [**v1.0**](/docs/dbt-versions/core-upgrade/older%20versions/upgrading-to-v1.0) | Dec 3, 2021 | End of Life* ⚠️ |
| **v0.X** ⛔️ | (Various dates) | Deprecated ⛔️ | Deprecated ⛔️ |
_*All versions of dbt Core since v1.0 are available in dbt Cloud until further notice. Versions that are EOL do not receive any fixes. For the best support, we recommend upgrading to a version released within the past 12 months._

0 comments on commit 4b8965a

Please sign in to comment.