From bd421b4b6444e8d7473183d91bb0cd5deaba7204 Mon Sep 17 00:00:00 2001 From: "Leona B. Campbell" <3880403+runleonarun@users.noreply.github.com> Date: Wed, 31 May 2023 16:25:34 -0700 Subject: [PATCH 01/24] Create may-ide-updates.md --- .../08-May-2023/may-ide-updates.md | 33 +++++++++++++++++++ 1 file changed, 33 insertions(+) create mode 100644 website/docs/docs/dbt-versions/release-notes/08-May-2023/may-ide-updates.md diff --git a/website/docs/docs/dbt-versions/release-notes/08-May-2023/may-ide-updates.md b/website/docs/docs/dbt-versions/release-notes/08-May-2023/may-ide-updates.md new file mode 100644 index 00000000000..98579af2fa1 --- /dev/null +++ b/website/docs/docs/dbt-versions/release-notes/08-May-2023/may-ide-updates.md @@ -0,0 +1,33 @@ +--- +title: "May IDE updates and fixes" +id: "may-ide-updates" +description: "May 2023 release note: We've ." +sidebar_label: "Update and fixes: IDE" +sidebar_position: 7 +tags: [May-2023, IDE] +--- + +To continue improving your [Cloud IDE](https://docs.getdbt.com/docs/cloud/develop-in-the-cloud) development experience, the dbt Labs team continues to work on adding new features, fixing bugs, and increasing reliability ✨. + +Stay up-to-date with [IDE-related changes](https://docs.getdbt.com/tags/ide). + +## New features +- Lint via SQLFluff in beta (reach out if interested, otherwise this will be available for multi-tenant soon!) +- Format markdown files with prettier +- Leverage developer experience shortcuts, including `Ctrl + `` (toggle history drawer), `CMD + Option + /` (toggle block comment), `CMD + Shift + P` (open command palette), `Option + W` (close editor tab) +- Display parent folder name for files with same name in Changes section +- Navigate the new IDE features quickly using [the IDE User Interface](https://docs.getdbt.com/docs/cloud/dbt-cloud-ide/ide-user-interface) help page +- Use `top X` in SQL when previewing in the IDE +- Opt into the new IDE backend layer over the past month (still with dbt-rpc). Ready for beta later in June! + + +## Product refinements +- Performance-related upgrades: + - Reduced cold start time by 60+% + - Improved render time of modals in the IDE by 98% + - Improved IDE performance with dbt Core v1.5+ (faster and snappier – highly encourage you to update your dbt version!) +- Upgraded sqlfmt (which powers the Format button) to 0.18.0 +- Updated Build button to change menu options based on file/model type (snapshot, macro, etc.) +- Display message to disable adblocker for file contents error +- Moved Format button to console bar +- Made many security enhancements in the IDE From 390b6553be40e05038bdd98277735b7b054cde9a Mon Sep 17 00:00:00 2001 From: "Leona B. Campbell" <3880403+runleonarun@users.noreply.github.com> Date: Wed, 31 May 2023 16:49:04 -0700 Subject: [PATCH 02/24] Update website/docs/docs/dbt-versions/release-notes/08-May-2023/may-ide-updates.md --- .../dbt-versions/release-notes/08-May-2023/may-ide-updates.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/docs/dbt-versions/release-notes/08-May-2023/may-ide-updates.md b/website/docs/docs/dbt-versions/release-notes/08-May-2023/may-ide-updates.md index 98579af2fa1..b070c5a8f21 100644 --- a/website/docs/docs/dbt-versions/release-notes/08-May-2023/may-ide-updates.md +++ b/website/docs/docs/dbt-versions/release-notes/08-May-2023/may-ide-updates.md @@ -3,7 +3,7 @@ title: "May IDE updates and fixes" id: "may-ide-updates" description: "May 2023 release note: We've ." sidebar_label: "Update and fixes: IDE" -sidebar_position: 7 +sidebar_position: 2 tags: [May-2023, IDE] --- From f3c32ff24d0f560b91fc3c17020d0e0852e48f5d Mon Sep 17 00:00:00 2001 From: "Leona B. Campbell" <3880403+runleonarun@users.noreply.github.com> Date: Wed, 31 May 2023 17:06:12 -0700 Subject: [PATCH 03/24] Update website/docs/docs/dbt-versions/release-notes/08-May-2023/may-ide-updates.md --- .../dbt-versions/release-notes/08-May-2023/may-ide-updates.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/docs/dbt-versions/release-notes/08-May-2023/may-ide-updates.md b/website/docs/docs/dbt-versions/release-notes/08-May-2023/may-ide-updates.md index b070c5a8f21..a059e8316d5 100644 --- a/website/docs/docs/dbt-versions/release-notes/08-May-2023/may-ide-updates.md +++ b/website/docs/docs/dbt-versions/release-notes/08-May-2023/may-ide-updates.md @@ -12,7 +12,7 @@ To continue improving your [Cloud IDE](https://docs.getdbt.com/docs/cloud/develo Stay up-to-date with [IDE-related changes](https://docs.getdbt.com/tags/ide). ## New features -- Lint via SQLFluff in beta (reach out if interested, otherwise this will be available for multi-tenant soon!) +- Lint via SQL Fluff is now available in beta (GA over the next 2-3 weeks) - Format markdown files with prettier - Leverage developer experience shortcuts, including `Ctrl + `` (toggle history drawer), `CMD + Option + /` (toggle block comment), `CMD + Shift + P` (open command palette), `Option + W` (close editor tab) - Display parent folder name for files with same name in Changes section From 951ffb19277faf18c44d38365f00e1259448c726 Mon Sep 17 00:00:00 2001 From: "Leona B. Campbell" <3880403+runleonarun@users.noreply.github.com> Date: Wed, 31 May 2023 17:07:22 -0700 Subject: [PATCH 04/24] Update website/docs/docs/dbt-versions/release-notes/08-May-2023/may-ide-updates.md --- .../dbt-versions/release-notes/08-May-2023/may-ide-updates.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/docs/dbt-versions/release-notes/08-May-2023/may-ide-updates.md b/website/docs/docs/dbt-versions/release-notes/08-May-2023/may-ide-updates.md index a059e8316d5..7d9cab248af 100644 --- a/website/docs/docs/dbt-versions/release-notes/08-May-2023/may-ide-updates.md +++ b/website/docs/docs/dbt-versions/release-notes/08-May-2023/may-ide-updates.md @@ -14,7 +14,7 @@ Stay up-to-date with [IDE-related changes](https://docs.getdbt.com/tags/ide). ## New features - Lint via SQL Fluff is now available in beta (GA over the next 2-3 weeks) - Format markdown files with prettier -- Leverage developer experience shortcuts, including `Ctrl + `` (toggle history drawer), `CMD + Option + /` (toggle block comment), `CMD + Shift + P` (open command palette), `Option + W` (close editor tab) +- Leverage developer experience shortcuts, including `Ctrl + /`` (toggle history drawer), `CMD + Option + /` (toggle block comment), `CMD + Shift + P` (open command palette), `Option + W` (close editor tab) - Display parent folder name for files with same name in Changes section - Navigate the new IDE features quickly using [the IDE User Interface](https://docs.getdbt.com/docs/cloud/dbt-cloud-ide/ide-user-interface) help page - Use `top X` in SQL when previewing in the IDE From a33c4e79cfa496c7c1cd766b6427690895d485ba Mon Sep 17 00:00:00 2001 From: "Leona B. Campbell" <3880403+runleonarun@users.noreply.github.com> Date: Wed, 31 May 2023 17:09:19 -0700 Subject: [PATCH 05/24] Update website/docs/docs/dbt-versions/release-notes/08-May-2023/may-ide-updates.md --- .../dbt-versions/release-notes/08-May-2023/may-ide-updates.md | 1 + 1 file changed, 1 insertion(+) diff --git a/website/docs/docs/dbt-versions/release-notes/08-May-2023/may-ide-updates.md b/website/docs/docs/dbt-versions/release-notes/08-May-2023/may-ide-updates.md index 7d9cab248af..aee5050061d 100644 --- a/website/docs/docs/dbt-versions/release-notes/08-May-2023/may-ide-updates.md +++ b/website/docs/docs/dbt-versions/release-notes/08-May-2023/may-ide-updates.md @@ -22,6 +22,7 @@ Stay up-to-date with [IDE-related changes](https://docs.getdbt.com/tags/ide). ## Product refinements + - Performance-related upgrades: - Reduced cold start time by 60+% - Improved render time of modals in the IDE by 98% From f53cafebce5d9a7db116b65c54b713588dd15135 Mon Sep 17 00:00:00 2001 From: "Leona B. Campbell" <3880403+runleonarun@users.noreply.github.com> Date: Wed, 31 May 2023 17:16:06 -0700 Subject: [PATCH 06/24] Update website/docs/docs/dbt-versions/release-notes/08-May-2023/may-ide-updates.md --- .../dbt-versions/release-notes/08-May-2023/may-ide-updates.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/docs/dbt-versions/release-notes/08-May-2023/may-ide-updates.md b/website/docs/docs/dbt-versions/release-notes/08-May-2023/may-ide-updates.md index aee5050061d..9a8b9a848ad 100644 --- a/website/docs/docs/dbt-versions/release-notes/08-May-2023/may-ide-updates.md +++ b/website/docs/docs/dbt-versions/release-notes/08-May-2023/may-ide-updates.md @@ -14,7 +14,7 @@ Stay up-to-date with [IDE-related changes](https://docs.getdbt.com/tags/ide). ## New features - Lint via SQL Fluff is now available in beta (GA over the next 2-3 weeks) - Format markdown files with prettier -- Leverage developer experience shortcuts, including `Ctrl + /`` (toggle history drawer), `CMD + Option + /` (toggle block comment), `CMD + Shift + P` (open command palette), `Option + W` (close editor tab) +- Leverage developer experience shortcuts, including `Ctrl + \`` (toggle history drawer), `CMD + Option + /` (toggle block comment), `CMD + Shift + P` (open command palette), `Option + W` (close editor tab) - Display parent folder name for files with same name in Changes section - Navigate the new IDE features quickly using [the IDE User Interface](https://docs.getdbt.com/docs/cloud/dbt-cloud-ide/ide-user-interface) help page - Use `top X` in SQL when previewing in the IDE From d94d16ff9ebc94e4960061b8e1fe8e9034f472c5 Mon Sep 17 00:00:00 2001 From: "Leona B. Campbell" <3880403+runleonarun@users.noreply.github.com> Date: Wed, 31 May 2023 17:16:18 -0700 Subject: [PATCH 07/24] Update website/docs/docs/dbt-versions/release-notes/08-May-2023/may-ide-updates.md --- .../release-notes/08-May-2023/may-ide-updates.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/website/docs/docs/dbt-versions/release-notes/08-May-2023/may-ide-updates.md b/website/docs/docs/dbt-versions/release-notes/08-May-2023/may-ide-updates.md index 9a8b9a848ad..10767ca35f9 100644 --- a/website/docs/docs/dbt-versions/release-notes/08-May-2023/may-ide-updates.md +++ b/website/docs/docs/dbt-versions/release-notes/08-May-2023/may-ide-updates.md @@ -32,3 +32,15 @@ Stay up-to-date with [IDE-related changes](https://docs.getdbt.com/tags/ide). - Display message to disable adblocker for file contents error - Moved Format button to console bar - Made many security enhancements in the IDE +## Bug fixes + +- File icon sizes no longer get wonky in small screen +- Toast notifications no longer take over command bar menu +- Hover info inside the text editor no longer gets cut off +- Transition between a file and a recently modified scratchpad no longer triggers a console error +- dbt v1.5+ now can access the IDE +- Confirm button on the Unsaved Changes modal now closes after clicking it +- Long node names no longer overflow in the parsed logs section in history drawer +- Status pill in history drawer no longer scales with longer command +- Tooltip for tab name with a long file name is no longer cut off +- Lint button should no longer available in main branch From f35c75ff00be016f0193abe361daaddcafe5b36e Mon Sep 17 00:00:00 2001 From: "Leona B. Campbell" <3880403+runleonarun@users.noreply.github.com> Date: Wed, 31 May 2023 17:16:52 -0700 Subject: [PATCH 08/24] Update website/docs/docs/dbt-versions/release-notes/08-May-2023/may-ide-updates.md --- .../dbt-versions/release-notes/08-May-2023/may-ide-updates.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/docs/dbt-versions/release-notes/08-May-2023/may-ide-updates.md b/website/docs/docs/dbt-versions/release-notes/08-May-2023/may-ide-updates.md index 10767ca35f9..b6c89b7ce60 100644 --- a/website/docs/docs/dbt-versions/release-notes/08-May-2023/may-ide-updates.md +++ b/website/docs/docs/dbt-versions/release-notes/08-May-2023/may-ide-updates.md @@ -14,7 +14,7 @@ Stay up-to-date with [IDE-related changes](https://docs.getdbt.com/tags/ide). ## New features - Lint via SQL Fluff is now available in beta (GA over the next 2-3 weeks) - Format markdown files with prettier -- Leverage developer experience shortcuts, including `Ctrl + \`` (toggle history drawer), `CMD + Option + /` (toggle block comment), `CMD + Shift + P` (open command palette), `Option + W` (close editor tab) +- Leverage developer experience shortcuts, including `Ctrl + \`` (toggle history drawer), `CMD + Option + \/` (toggle block comment), `CMD + Shift + P` (open command palette), `Option + W` (close editor tab) - Display parent folder name for files with same name in Changes section - Navigate the new IDE features quickly using [the IDE User Interface](https://docs.getdbt.com/docs/cloud/dbt-cloud-ide/ide-user-interface) help page - Use `top X` in SQL when previewing in the IDE From 136c34041b6f2683a5314666b0ac0a994d07fd18 Mon Sep 17 00:00:00 2001 From: "Leona B. Campbell" <3880403+runleonarun@users.noreply.github.com> Date: Wed, 31 May 2023 17:22:39 -0700 Subject: [PATCH 09/24] Update website/docs/docs/dbt-versions/release-notes/08-May-2023/may-ide-updates.md --- .../dbt-versions/release-notes/08-May-2023/may-ide-updates.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/docs/dbt-versions/release-notes/08-May-2023/may-ide-updates.md b/website/docs/docs/dbt-versions/release-notes/08-May-2023/may-ide-updates.md index b6c89b7ce60..a9471853a4b 100644 --- a/website/docs/docs/dbt-versions/release-notes/08-May-2023/may-ide-updates.md +++ b/website/docs/docs/dbt-versions/release-notes/08-May-2023/may-ide-updates.md @@ -14,7 +14,7 @@ Stay up-to-date with [IDE-related changes](https://docs.getdbt.com/tags/ide). ## New features - Lint via SQL Fluff is now available in beta (GA over the next 2-3 weeks) - Format markdown files with prettier -- Leverage developer experience shortcuts, including `Ctrl + \`` (toggle history drawer), `CMD + Option + \/` (toggle block comment), `CMD + Shift + P` (open command palette), `Option + W` (close editor tab) +- Leverage developer experience shortcuts, including ``Ctrl +` `` (toggle history drawer), `CMD + Option + /` (toggle block comment), `CMD + Shift + P` (open command palette), `Option + W` (close editor tab) - Display parent folder name for files with same name in Changes section - Navigate the new IDE features quickly using [the IDE User Interface](https://docs.getdbt.com/docs/cloud/dbt-cloud-ide/ide-user-interface) help page - Use `top X` in SQL when previewing in the IDE From 901aaa1b821170cfa74b265742f81c52b52f2313 Mon Sep 17 00:00:00 2001 From: mirnawong1 <89008547+mirnawong1@users.noreply.github.com> Date: Thu, 1 Jun 2023 10:44:26 +0100 Subject: [PATCH 10/24] Update website/docs/docs/dbt-versions/release-notes/08-May-2023/may-ide-updates.md --- .../dbt-versions/release-notes/08-May-2023/may-ide-updates.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/docs/dbt-versions/release-notes/08-May-2023/may-ide-updates.md b/website/docs/docs/dbt-versions/release-notes/08-May-2023/may-ide-updates.md index a9471853a4b..9b089b4d325 100644 --- a/website/docs/docs/dbt-versions/release-notes/08-May-2023/may-ide-updates.md +++ b/website/docs/docs/dbt-versions/release-notes/08-May-2023/may-ide-updates.md @@ -7,7 +7,7 @@ sidebar_position: 2 tags: [May-2023, IDE] --- -To continue improving your [Cloud IDE](https://docs.getdbt.com/docs/cloud/develop-in-the-cloud) development experience, the dbt Labs team continues to work on adding new features, fixing bugs, and increasing reliability ✨. +To continue improving your [Cloud IDE](/docs/cloud/develop-in-the-cloud) development experience, the dbt Labs team continues to work on adding new features, fixing bugs, and increasing reliability ✨. Stay up-to-date with [IDE-related changes](https://docs.getdbt.com/tags/ide). From 3d3d010f190668cf93ec9ae774a577365ce119cc Mon Sep 17 00:00:00 2001 From: mirnawong1 <89008547+mirnawong1@users.noreply.github.com> Date: Thu, 1 Jun 2023 10:44:43 +0100 Subject: [PATCH 11/24] Update website/docs/docs/dbt-versions/release-notes/08-May-2023/may-ide-updates.md --- .../dbt-versions/release-notes/08-May-2023/may-ide-updates.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/docs/dbt-versions/release-notes/08-May-2023/may-ide-updates.md b/website/docs/docs/dbt-versions/release-notes/08-May-2023/may-ide-updates.md index 9b089b4d325..db9f9ef9f16 100644 --- a/website/docs/docs/dbt-versions/release-notes/08-May-2023/may-ide-updates.md +++ b/website/docs/docs/dbt-versions/release-notes/08-May-2023/may-ide-updates.md @@ -9,7 +9,7 @@ tags: [May-2023, IDE] To continue improving your [Cloud IDE](/docs/cloud/develop-in-the-cloud) development experience, the dbt Labs team continues to work on adding new features, fixing bugs, and increasing reliability ✨. -Stay up-to-date with [IDE-related changes](https://docs.getdbt.com/tags/ide). +Stay up-to-date with [IDE-related changes](/tags/ide). ## New features - Lint via SQL Fluff is now available in beta (GA over the next 2-3 weeks) From 4923080f90906eb78350087388677e1a49a63c99 Mon Sep 17 00:00:00 2001 From: mirnawong1 <89008547+mirnawong1@users.noreply.github.com> Date: Thu, 1 Jun 2023 11:23:54 +0100 Subject: [PATCH 12/24] Update website/docs/docs/dbt-versions/release-notes/08-May-2023/may-ide-updates.md --- .../dbt-versions/release-notes/08-May-2023/may-ide-updates.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/docs/dbt-versions/release-notes/08-May-2023/may-ide-updates.md b/website/docs/docs/dbt-versions/release-notes/08-May-2023/may-ide-updates.md index db9f9ef9f16..469f86f1d6e 100644 --- a/website/docs/docs/dbt-versions/release-notes/08-May-2023/may-ide-updates.md +++ b/website/docs/docs/dbt-versions/release-notes/08-May-2023/may-ide-updates.md @@ -7,7 +7,7 @@ sidebar_position: 2 tags: [May-2023, IDE] --- -To continue improving your [Cloud IDE](/docs/cloud/develop-in-the-cloud) development experience, the dbt Labs team continues to work on adding new features, fixing bugs, and increasing reliability ✨. +To continue improving your [Cloud IDE](/docs/cloud/dbt-cloud-ide/develop-in-the-cloud) development experience, the dbt Labs team continues to work on adding new features, fixing bugs, and increasing reliability ✨. Stay up-to-date with [IDE-related changes](/tags/ide). From 3201b4dac40784ba597631d68394dac273a538b7 Mon Sep 17 00:00:00 2001 From: mirnawong1 <89008547+mirnawong1@users.noreply.github.com> Date: Thu, 1 Jun 2023 11:24:19 +0100 Subject: [PATCH 13/24] Update website/docs/docs/dbt-versions/release-notes/08-May-2023/may-ide-updates.md --- .../dbt-versions/release-notes/08-May-2023/may-ide-updates.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/docs/dbt-versions/release-notes/08-May-2023/may-ide-updates.md b/website/docs/docs/dbt-versions/release-notes/08-May-2023/may-ide-updates.md index 469f86f1d6e..9a5f2f14b7f 100644 --- a/website/docs/docs/dbt-versions/release-notes/08-May-2023/may-ide-updates.md +++ b/website/docs/docs/dbt-versions/release-notes/08-May-2023/may-ide-updates.md @@ -16,7 +16,7 @@ Stay up-to-date with [IDE-related changes](/tags/ide). - Format markdown files with prettier - Leverage developer experience shortcuts, including ``Ctrl +` `` (toggle history drawer), `CMD + Option + /` (toggle block comment), `CMD + Shift + P` (open command palette), `Option + W` (close editor tab) - Display parent folder name for files with same name in Changes section -- Navigate the new IDE features quickly using [the IDE User Interface](https://docs.getdbt.com/docs/cloud/dbt-cloud-ide/ide-user-interface) help page +- Navigate the new IDE features quickly using [the IDE User Interface](/docs/cloud/dbt-cloud-ide/ide-user-interface) help page - Use `top X` in SQL when previewing in the IDE - Opt into the new IDE backend layer over the past month (still with dbt-rpc). Ready for beta later in June! From 701a1d46c9c3a632be1d2ad693ec28009de57dec Mon Sep 17 00:00:00 2001 From: rpourzand Date: Tue, 29 Aug 2023 14:39:23 -0700 Subject: [PATCH 14/24] Update sl-partner-integration-guide.md Making a few more recommendations based on our API functionality --- .../docs/guides/dbt-ecosystem/sl-partner-integration-guide.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/website/docs/guides/dbt-ecosystem/sl-partner-integration-guide.md b/website/docs/guides/dbt-ecosystem/sl-partner-integration-guide.md index d707200cd46..9a9b6145916 100644 --- a/website/docs/guides/dbt-ecosystem/sl-partner-integration-guide.md +++ b/website/docs/guides/dbt-ecosystem/sl-partner-integration-guide.md @@ -50,7 +50,7 @@ When working with more governed data, it's essential to establish clear guardrai - **Aggregations control** — Users shouldn't generally be allowed to modify aggregations unless they perform post-processing calculations on Semantic Layer data (such as year-over-year analysis). -- **Time series alignment and using metric_time** — Make sure users view metrics across the correct time series. When displaying metric graphs, using a non-default time aggregation dimension might lead to misleading interpretations. While users can still group by other time dimensions, they should be careful not to create trend lines with incorrect time axes.

When looking at one or multiple metrics, users should use `metric_time` as the main time dimension to guarantee they are looking at the right time series for the metric(s).

As such, when building an application, we recommend exposing `metric_time` as a separate, "special" time dimension on its own. This dimension is always going to align with all metrics and be common across them. Other time dimensions can still be looked at and grouped by, but having a clear delineation between the `metric_time` dimension and the other time dimensions is clarifying so that people do not confuse how metrics should be plotted.

Also, when a user requests a time granularity change for the main time series, the query that your application runs should use `metric_time` as this will always give you the correct slice. Note that when looking at a single metric, the primary time dimension and `metric_time` are equivalent. +- **Time series alignment and using metric_time** — Make sure users view metrics across the correct time series. When displaying metric graphs, using a non-default time aggregation dimension might lead to misleading interpretations. While users can still group by other time dimensions, they should be careful not to create trend lines with incorrect time axes.

When looking at one or multiple metrics, users should use `metric_time` as the main time dimension to guarantee they are looking at the right time series for the metric(s).

As such, when building an application, we recommend exposing `metric_time` as a separate, "special" time dimension on its own. This dimension is always going to align with all metrics and be common across them. Other time dimensions can still be looked at and grouped by, but having a clear delineation between the `metric_time` dimension and the other time dimensions is clarifying so that people do not confuse how metrics should be plotted.

Also, when a user requests a time granularity change for the main time series, the query that your application runs should use `metric_time` as this will always give you the correct slice. Related to thsi, we do also strongly recommend that you have a way to expose what dimension `metric_time` actually maps to for users who may not be familiar. Our APIs allow you to fetch the actual underlying time dimensions that make up metric_time (e.g., transaction_date) so you can expose them to your users. - **Units consistency** — If units are supported, it's vital to avoid plotting data incorrectly with different units. Ensuring consistency in unit representation will prevent confusion and misinterpretation of the data. @@ -90,7 +90,7 @@ Allow users to query either one metric alone without dimensions or multiple metr - Only expose time granularities (monthly, daily, yearly) that match the available metrics. * For example, if a dbt model and its resulting semantic model have a monthly granularity, make sure querying data with a 'daily' granularity isn't available to the user. Our APIs have functionality that will help you surface the correct granularities -- We recommend that time granularity is treated as a general time dimension-specific concept and that it can be applied to more than just the primary aggregation (or `metric_time`). Consider a situation where a user wants to look at `sales` over time by `customer signup month`; in this situation, having the ability to apply granularities to both time dimensions is crucial. Note: Initially, as a starting point, it makes sense to only support `metric_time` or the primary time dimension, but we recommend expanding that as your solution evolves. +- We recommend that time granularity is treated as a general time dimension-specific concept and that it can be applied to more than just the primary aggregation (or `metric_time`). Consider a situation where a user wants to look at `sales` over time by `customer signup month`; in this situation, having the ability to apply granularities to both time dimensions is crucial. Our APIs include information to fetch the granularities for the primary (metric_time) dimensions, but as well as all time dimensions, so you can treat each time dimension and granularity selection independently in your application. Note: Initially, as a starting point, it makes sense to only support `metric_time` or the primary time dimension, but we recommend expanding that as your solution evolves. - You should allow users to filter on date ranges and expose a calendar and nice presets for filtering these. * For example, last 30 days, last week, and so on. From b49a727dc968fd67d6d57157a657f36682f1b8af Mon Sep 17 00:00:00 2001 From: rpourzand Date: Tue, 29 Aug 2023 14:40:34 -0700 Subject: [PATCH 15/24] Update sl-partner-integration-guide.md typo fix! --- .../docs/guides/dbt-ecosystem/sl-partner-integration-guide.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/guides/dbt-ecosystem/sl-partner-integration-guide.md b/website/docs/guides/dbt-ecosystem/sl-partner-integration-guide.md index 9a9b6145916..10f5cf9910f 100644 --- a/website/docs/guides/dbt-ecosystem/sl-partner-integration-guide.md +++ b/website/docs/guides/dbt-ecosystem/sl-partner-integration-guide.md @@ -50,7 +50,7 @@ When working with more governed data, it's essential to establish clear guardrai - **Aggregations control** — Users shouldn't generally be allowed to modify aggregations unless they perform post-processing calculations on Semantic Layer data (such as year-over-year analysis). -- **Time series alignment and using metric_time** — Make sure users view metrics across the correct time series. When displaying metric graphs, using a non-default time aggregation dimension might lead to misleading interpretations. While users can still group by other time dimensions, they should be careful not to create trend lines with incorrect time axes.

When looking at one or multiple metrics, users should use `metric_time` as the main time dimension to guarantee they are looking at the right time series for the metric(s).

As such, when building an application, we recommend exposing `metric_time` as a separate, "special" time dimension on its own. This dimension is always going to align with all metrics and be common across them. Other time dimensions can still be looked at and grouped by, but having a clear delineation between the `metric_time` dimension and the other time dimensions is clarifying so that people do not confuse how metrics should be plotted.

Also, when a user requests a time granularity change for the main time series, the query that your application runs should use `metric_time` as this will always give you the correct slice. Related to thsi, we do also strongly recommend that you have a way to expose what dimension `metric_time` actually maps to for users who may not be familiar. Our APIs allow you to fetch the actual underlying time dimensions that make up metric_time (e.g., transaction_date) so you can expose them to your users. +- **Time series alignment and using metric_time** — Make sure users view metrics across the correct time series. When displaying metric graphs, using a non-default time aggregation dimension might lead to misleading interpretations. While users can still group by other time dimensions, they should be careful not to create trend lines with incorrect time axes.

When looking at one or multiple metrics, users should use `metric_time` as the main time dimension to guarantee they are looking at the right time series for the metric(s).

As such, when building an application, we recommend exposing `metric_time` as a separate, "special" time dimension on its own. This dimension is always going to align with all metrics and be common across them. Other time dimensions can still be looked at and grouped by, but having a clear delineation between the `metric_time` dimension and the other time dimensions is clarifying so that people do not confuse how metrics should be plotted.

Also, when a user requests a time granularity change for the main time series, the query that your application runs should use `metric_time` as this will always give you the correct slice. Related to this, we do also strongly recommend that you have a way to expose what dimension `metric_time` actually maps to for users who may not be familiar. Our APIs allow you to fetch the actual underlying time dimensions that make up metric_time (e.g., transaction_date) so you can expose them to your users. - **Units consistency** — If units are supported, it's vital to avoid plotting data incorrectly with different units. Ensuring consistency in unit representation will prevent confusion and misinterpretation of the data. From 0cd65a15ba61e5f5b74cc199c8c5d00fd7cef18f Mon Sep 17 00:00:00 2001 From: "Leona B. Campbell" <3880403+runleonarun@users.noreply.github.com> Date: Tue, 29 Aug 2023 16:29:48 -0700 Subject: [PATCH 16/24] Update redshift-configs.md --- website/docs/reference/resource-configs/redshift-configs.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/website/docs/reference/resource-configs/redshift-configs.md b/website/docs/reference/resource-configs/redshift-configs.md index d751e702e27..13f2562e677 100644 --- a/website/docs/reference/resource-configs/redshift-configs.md +++ b/website/docs/reference/resource-configs/redshift-configs.md @@ -15,13 +15,18 @@ To-do: In dbt-redshift, the following incremental materialization strategies are supported: + - `append` (default) - `delete+insert` + + + - `append` (default) - `merge` - `delete+insert` + All of these strategies are inheirited via from dbt-postgres. From fed1bd1144751596139f0eebe11cc3981898749b Mon Sep 17 00:00:00 2001 From: "Leona B. Campbell" <3880403+runleonarun@users.noreply.github.com> Date: Tue, 29 Aug 2023 17:42:59 -0700 Subject: [PATCH 17/24] Update website/docs/reference/resource-configs/redshift-configs.md --- website/docs/reference/resource-configs/redshift-configs.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/reference/resource-configs/redshift-configs.md b/website/docs/reference/resource-configs/redshift-configs.md index 13f2562e677..04bdc59f96a 100644 --- a/website/docs/reference/resource-configs/redshift-configs.md +++ b/website/docs/reference/resource-configs/redshift-configs.md @@ -29,7 +29,7 @@ In dbt-redshift, the following incremental materialization strategies are suppor -All of these strategies are inheirited via from dbt-postgres. +All of these strategies are inherited via from dbt-postgres. ## Performance optimizations From 58f9c6a0a188c95b1d17b6e6679be0bb4490baf4 Mon Sep 17 00:00:00 2001 From: "Leona B. Campbell" <3880403+runleonarun@users.noreply.github.com> Date: Tue, 29 Aug 2023 17:46:13 -0700 Subject: [PATCH 18/24] Update website/docs/reference/resource-configs/redshift-configs.md --- website/docs/reference/resource-configs/redshift-configs.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/reference/resource-configs/redshift-configs.md b/website/docs/reference/resource-configs/redshift-configs.md index 04bdc59f96a..474f395d124 100644 --- a/website/docs/reference/resource-configs/redshift-configs.md +++ b/website/docs/reference/resource-configs/redshift-configs.md @@ -14,7 +14,7 @@ To-do: In dbt-redshift, the following incremental materialization strategies are supported: - + - `append` (default) - `delete+insert` From 9f212cbbd3a387168642d191d821a43e91413565 Mon Sep 17 00:00:00 2001 From: "Leona B. Campbell" <3880403+runleonarun@users.noreply.github.com> Date: Tue, 29 Aug 2023 17:57:35 -0700 Subject: [PATCH 19/24] Update cloud-feature-parity.md --- website/snippets/cloud-feature-parity.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/snippets/cloud-feature-parity.md b/website/snippets/cloud-feature-parity.md index 31644343908..1adfb5882c2 100644 --- a/website/snippets/cloud-feature-parity.md +++ b/website/snippets/cloud-feature-parity.md @@ -10,5 +10,5 @@ The following table outlines which dbt Cloud features are supported on the diffe | Continuous Integration, including CI jobs | ✅ | ✅ | ✅ | | Semantic Layer | ✅ (North America Only) | ❌ | ❌ | | IP Restrictions | ✅ | ✅ | ✅ | -| PrivateLink egress | ✅ | ✅ | ✅ | +| PrivateLink egress | ✅ (AWS only)| ✅ | ✅ | | PrivateLink ingress | ❌ | ✅ | ✅ | From acd2eafab4212d236e5547f982ec779ca3a7dfb8 Mon Sep 17 00:00:00 2001 From: "Leona B. Campbell" <3880403+runleonarun@users.noreply.github.com> Date: Tue, 29 Aug 2023 18:01:50 -0700 Subject: [PATCH 20/24] Update website/docs/reference/resource-configs/redshift-configs.md --- website/docs/reference/resource-configs/redshift-configs.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/reference/resource-configs/redshift-configs.md b/website/docs/reference/resource-configs/redshift-configs.md index 474f395d124..04bdc59f96a 100644 --- a/website/docs/reference/resource-configs/redshift-configs.md +++ b/website/docs/reference/resource-configs/redshift-configs.md @@ -14,7 +14,7 @@ To-do: In dbt-redshift, the following incremental materialization strategies are supported: - + - `append` (default) - `delete+insert` From 544f87ea87ffb643410782d9d07c2ca60a9d40e3 Mon Sep 17 00:00:00 2001 From: mirnawong1 Date: Wed, 30 Aug 2023 09:44:04 +0100 Subject: [PATCH 21/24] fix spcing for versionblock --- website/docs/reference/resource-configs/redshift-configs.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/website/docs/reference/resource-configs/redshift-configs.md b/website/docs/reference/resource-configs/redshift-configs.md index 04bdc59f96a..9bd127a1e1a 100644 --- a/website/docs/reference/resource-configs/redshift-configs.md +++ b/website/docs/reference/resource-configs/redshift-configs.md @@ -15,7 +15,7 @@ To-do: In dbt-redshift, the following incremental materialization strategies are supported: - + - `append` (default) - `delete+insert` @@ -29,13 +29,13 @@ In dbt-redshift, the following incremental materialization strategies are suppor -All of these strategies are inherited via from dbt-postgres. +All of these strategies are inherited from dbt-postgres. ## Performance optimizations ### Using sortkey and distkey -Tables in Amazon Redshift have two powerful optimizations to improve query performance: distkeys and sortkeys. Supplying these values as model-level configurations apply the corresponding settings in the generated `CREATE TABLE` . Note that these settings will have no effect for models set to `view` or `ephemeral` models. +Tables in Amazon Redshift have two powerful optimizations to improve query performance: distkeys and sortkeys. Supplying these values as model-level configurations apply the corresponding settings in the generated `CREATE TABLE` . Note that these settings will have no effect on models set to `view` or `ephemeral` models. - `dist` can have a setting of `all`, `even`, `auto`, or the name of a key. - `sort` accepts a list of sort keys, for example: `['timestamp', 'userid']`. dbt will build the sort key in the same order the fields are supplied. From 52eb7800de9a1bd8f377afffcc73f7d81b1a6170 Mon Sep 17 00:00:00 2001 From: mirnawong1 <89008547+mirnawong1@users.noreply.github.com> Date: Wed, 30 Aug 2023 09:46:31 +0100 Subject: [PATCH 22/24] Update website/docs/guides/dbt-ecosystem/sl-partner-integration-guide.md --- .../docs/guides/dbt-ecosystem/sl-partner-integration-guide.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/guides/dbt-ecosystem/sl-partner-integration-guide.md b/website/docs/guides/dbt-ecosystem/sl-partner-integration-guide.md index 10f5cf9910f..549e065b014 100644 --- a/website/docs/guides/dbt-ecosystem/sl-partner-integration-guide.md +++ b/website/docs/guides/dbt-ecosystem/sl-partner-integration-guide.md @@ -50,7 +50,7 @@ When working with more governed data, it's essential to establish clear guardrai - **Aggregations control** — Users shouldn't generally be allowed to modify aggregations unless they perform post-processing calculations on Semantic Layer data (such as year-over-year analysis). -- **Time series alignment and using metric_time** — Make sure users view metrics across the correct time series. When displaying metric graphs, using a non-default time aggregation dimension might lead to misleading interpretations. While users can still group by other time dimensions, they should be careful not to create trend lines with incorrect time axes.

When looking at one or multiple metrics, users should use `metric_time` as the main time dimension to guarantee they are looking at the right time series for the metric(s).

As such, when building an application, we recommend exposing `metric_time` as a separate, "special" time dimension on its own. This dimension is always going to align with all metrics and be common across them. Other time dimensions can still be looked at and grouped by, but having a clear delineation between the `metric_time` dimension and the other time dimensions is clarifying so that people do not confuse how metrics should be plotted.

Also, when a user requests a time granularity change for the main time series, the query that your application runs should use `metric_time` as this will always give you the correct slice. Related to this, we do also strongly recommend that you have a way to expose what dimension `metric_time` actually maps to for users who may not be familiar. Our APIs allow you to fetch the actual underlying time dimensions that make up metric_time (e.g., transaction_date) so you can expose them to your users. +- **Time series alignment and using metric_time** — Make sure users view metrics across the correct time series. When displaying metric graphs, using a non-default time aggregation dimension might lead to misleading interpretations. While users can still group by other time dimensions, they should be careful not to create trend lines with incorrect time axes.

When looking at one or multiple metrics, users should use `metric_time` as the main time dimension to guarantee they are looking at the right time series for the metric(s).

As such, when building an application, we recommend exposing `metric_time` as a separate, "special" time dimension on its own. This dimension is always going to align with all metrics and be common across them. Other time dimensions can still be looked at and grouped by, but having a clear delineation between the `metric_time` dimension and the other time dimensions is clarifying so that people do not confuse how metrics should be plotted.

Also, when a user requests a time granularity change for the main time series, the query that your application runs should use `metric_time` as this will always give you the correct slice. Related to this, we also strongly recommend that you have a way to expose what dimension `metric_time` actually maps to for users who may not be familiar. Our APIs allow you to fetch the actual underlying time dimensions that makeup metric_time (such as `transaction_date`) so you can expose them to your users. - **Units consistency** — If units are supported, it's vital to avoid plotting data incorrectly with different units. Ensuring consistency in unit representation will prevent confusion and misinterpretation of the data. From 210601c7618933d43bf2554d99c7bdd320d9a030 Mon Sep 17 00:00:00 2001 From: mirnawong1 <89008547+mirnawong1@users.noreply.github.com> Date: Wed, 30 Aug 2023 09:48:47 +0100 Subject: [PATCH 23/24] Update website/docs/guides/dbt-ecosystem/sl-partner-integration-guide.md --- .../docs/guides/dbt-ecosystem/sl-partner-integration-guide.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/guides/dbt-ecosystem/sl-partner-integration-guide.md b/website/docs/guides/dbt-ecosystem/sl-partner-integration-guide.md index 549e065b014..20e2d8fce71 100644 --- a/website/docs/guides/dbt-ecosystem/sl-partner-integration-guide.md +++ b/website/docs/guides/dbt-ecosystem/sl-partner-integration-guide.md @@ -90,7 +90,7 @@ Allow users to query either one metric alone without dimensions or multiple metr - Only expose time granularities (monthly, daily, yearly) that match the available metrics. * For example, if a dbt model and its resulting semantic model have a monthly granularity, make sure querying data with a 'daily' granularity isn't available to the user. Our APIs have functionality that will help you surface the correct granularities -- We recommend that time granularity is treated as a general time dimension-specific concept and that it can be applied to more than just the primary aggregation (or `metric_time`). Consider a situation where a user wants to look at `sales` over time by `customer signup month`; in this situation, having the ability to apply granularities to both time dimensions is crucial. Our APIs include information to fetch the granularities for the primary (metric_time) dimensions, but as well as all time dimensions, so you can treat each time dimension and granularity selection independently in your application. Note: Initially, as a starting point, it makes sense to only support `metric_time` or the primary time dimension, but we recommend expanding that as your solution evolves. +- We recommend that time granularity is treated as a general time dimension-specific concept and that it can be applied to more than just the primary aggregation (or `metric_time`). Consider a situation where a user wants to look at `sales` over time by `customer signup month`; in this situation, having the ability to apply granularities to both time dimensions is crucial. Our APIs include information to fetch the granularities for the primary (metric_time) dimensions, as well as all time dimensions. You can treat each time dimension and granularity selection independently in your application. Note: Initially, as a starting point, it makes sense to only support `metric_time` or the primary time dimension, but we recommend expanding that as your solution evolves. - You should allow users to filter on date ranges and expose a calendar and nice presets for filtering these. * For example, last 30 days, last week, and so on. From cd5c34991176e4f6d738b71b3ae7727c4b2419f0 Mon Sep 17 00:00:00 2001 From: mirnawong1 <89008547+mirnawong1@users.noreply.github.com> Date: Wed, 30 Aug 2023 09:51:12 +0100 Subject: [PATCH 24/24] Update may-ide-updates.md --- .../08-May-2023/may-ide-updates.md | 46 +++++++++++++++++++ 1 file changed, 46 insertions(+) diff --git a/website/docs/docs/dbt-versions/release-notes/08-May-2023/may-ide-updates.md b/website/docs/docs/dbt-versions/release-notes/08-May-2023/may-ide-updates.md index e69de29bb2d..d85ffa154dd 100644 --- a/website/docs/docs/dbt-versions/release-notes/08-May-2023/may-ide-updates.md +++ b/website/docs/docs/dbt-versions/release-notes/08-May-2023/may-ide-updates.md @@ -0,0 +1,46 @@ +--- +title: "May IDE updates and fixes" +id: "may-ide-updates" +description: "May 2023 release note: We've launched SQLFluff in beta, released an IDE UI page, significantly improved IDE performance, improved error messages, fixed bugs, and more." +sidebar_label: "Update and fixes: IDE" +sidebar_position: 2 +tags: [May-2023, IDE] +--- + +To continue improving your [Cloud IDE](/docs/cloud/dbt-cloud-ide/develop-in-the-cloud) development experience, the dbt Labs team continues to work on adding new features, fixing bugs, and increasing reliability ✨. + +Stay up-to-date with [IDE-related changes](/tags/ide). + +## New features +- Lint via SQL Fluff is now available in beta (GA over the next 2-3 weeks) +- Format markdown files with prettier +- Leverage developer experience shortcuts, including ``Ctrl + ` `` (toggle history drawer), `CMD + Option + /` (toggle block comment), `CMD + Shift + P` (open command palette), `Option + W` (close editor tab) +- Display parent folder name for files with same name in Changes section +- Navigate the new IDE features quickly using [the IDE User Interface](/docs/cloud/dbt-cloud-ide/ide-user-interface) help page +- Use `top X` in SQL when previewing in the IDE +- Opt into the new IDE backend layer over the past month (still with dbt-rpc). Ready for beta later in June! + + +## Product refinements + +- Performance-related upgrades: + - Reduced cold start time by 60+% + - Improved render time of modals in the IDE by 98% + - Improved IDE performance with dbt Core v1.5+ (faster and snappier – highly encourage you to [upgrade your dbt version](/docs/dbt-versions/upgrade-core-in-cloud)!) +- Upgraded sqlfmt (which powers the Format button) to 0.18.0 +- Updated Build button to change menu options based on file/model type (snapshot, macro, etc.) +- Display message to disable adblocker for file contents error +- Moved Format button to console bar +- Made many security enhancements in the IDE +## Bug fixes + +- File icon sizes no longer get wonky in small screen +- Toast notifications no longer take over command bar menu +- Hover info inside the text editor no longer gets cut off +- Transition between a file and a recently modified scratchpad no longer triggers a console error +- dbt v1.5+ now can access the IDE +- Confirm button on the Unsaved Changes modal now closes after clicking it +- Long node names no longer overflow in the parsed logs section in history drawer +- Status pill in history drawer no longer scales with longer command +- Tooltip for tab name with a long file name is no longer cut off +- Lint button should no longer available in main branch