From f4693b9813897634602b27fdea54d8089f509633 Mon Sep 17 00:00:00 2001 From: mirnawong1 Date: Mon, 18 Dec 2023 13:57:28 -0500 Subject: [PATCH 01/20] add rn --- .../74-Dec-2023/dec-sl-updates.md | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) create mode 100644 website/docs/docs/dbt-versions/release-notes/74-Dec-2023/dec-sl-updates.md diff --git a/website/docs/docs/dbt-versions/release-notes/74-Dec-2023/dec-sl-updates.md b/website/docs/docs/dbt-versions/release-notes/74-Dec-2023/dec-sl-updates.md new file mode 100644 index 00000000000..3f43222685a --- /dev/null +++ b/website/docs/docs/dbt-versions/release-notes/74-Dec-2023/dec-sl-updates.md @@ -0,0 +1,19 @@ +--- +title: “Updates and fixes: dbt Semantic Layer and MetricFlow updates for the month of December 2023.” +description: “December 2023: Enhanced Tableau integration, BIGINT support, LookML to MetricFlow conversion, and deprecation of legacy features.” +sidebar_label: “Update ad fixes: dbt Semantic Layer and MetricFlow.” +sidebar_position: 08 +date: 2023-12-22 +--- +The dbt Labs team continues to work on adding new features, fixing bugs, and increasing reliability for the dbt Semantic Layer and MetricFlow. Here are the updates and fixes for the month of December 2023. + +## Bug fixes +- The dbt Semantic Layer integration with Tableau now supports using exclude in its user interface. Previously it wasn’t supported. +- The dbt Semantic Layer can support `BIGINT` with over 18 digits. Previously it would return an error. +- The [dbt converter tool](https://github.com/dbt-labs/dbt-converter) can now convert data definitions from LookML to MetricFlow and help users upgrade. Previously this wasn’t available. (converts from lookml to metricflow specs). ROXI TO CLARIFY WITH NICK TO DETERMINE IF WE WANT TO TALK ABOUT THIS NOW OR LATER ON WHEN IT HAS MORE FEATURES. + +## Improvements +- dbt Labs deprecated [dbt Metrics and the legacy dbt Semantic Layer](/docs/dbt-versions/release-notes/Dec-2023/legacy-sl), both supported on dbt version 1.5 or lower. This change came into effect on December 15th, 2023. + +## New features +- Test From 8117a3cdee24c10b139daacc8289ae7204428c41 Mon Sep 17 00:00:00 2001 From: mirnawong1 <89008547+mirnawong1@users.noreply.github.com> Date: Mon, 18 Dec 2023 14:10:03 -0500 Subject: [PATCH 02/20] Update dec-sl-updates.md --- .../release-notes/74-Dec-2023/dec-sl-updates.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/website/docs/docs/dbt-versions/release-notes/74-Dec-2023/dec-sl-updates.md b/website/docs/docs/dbt-versions/release-notes/74-Dec-2023/dec-sl-updates.md index 3f43222685a..b2db3ef7adb 100644 --- a/website/docs/docs/dbt-versions/release-notes/74-Dec-2023/dec-sl-updates.md +++ b/website/docs/docs/dbt-versions/release-notes/74-Dec-2023/dec-sl-updates.md @@ -1,11 +1,11 @@ --- -title: “Updates and fixes: dbt Semantic Layer and MetricFlow updates for the month of December 2023.” -description: “December 2023: Enhanced Tableau integration, BIGINT support, LookML to MetricFlow conversion, and deprecation of legacy features.” -sidebar_label: “Update ad fixes: dbt Semantic Layer and MetricFlow.” +title: "Updates and fixes: dbt Semantic Layer and MetricFlow updates for December 2023." +description: "December 2023: Enhanced Tableau integration, BIGINT support, LookML to MetricFlow conversion, and deprecation of legacy features." +sidebar_label: "Update ad fixes: dbt Semantic Layer and MetricFlow." sidebar_position: 08 date: 2023-12-22 --- -The dbt Labs team continues to work on adding new features, fixing bugs, and increasing reliability for the dbt Semantic Layer and MetricFlow. Here are the updates and fixes for the month of December 2023. +The dbt Labs team continues to work on adding new features, fixing bugs, and increasing reliability for the dbt Semantic Layer and MetricFlow. Here are the updates and fixes for December 2023. ## Bug fixes - The dbt Semantic Layer integration with Tableau now supports using exclude in its user interface. Previously it wasn’t supported. From 17dcbc1cc80a08f19e2dbd274d3fd2cce230afb8 Mon Sep 17 00:00:00 2001 From: rpourzand Date: Mon, 18 Dec 2023 11:50:02 -0800 Subject: [PATCH 03/20] Update dec-sl-updates.md A couple of edits after talking to the team! --- .../dbt-versions/release-notes/74-Dec-2023/dec-sl-updates.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/website/docs/docs/dbt-versions/release-notes/74-Dec-2023/dec-sl-updates.md b/website/docs/docs/dbt-versions/release-notes/74-Dec-2023/dec-sl-updates.md index b2db3ef7adb..cfdc8dd8b69 100644 --- a/website/docs/docs/dbt-versions/release-notes/74-Dec-2023/dec-sl-updates.md +++ b/website/docs/docs/dbt-versions/release-notes/74-Dec-2023/dec-sl-updates.md @@ -8,12 +8,13 @@ date: 2023-12-22 The dbt Labs team continues to work on adding new features, fixing bugs, and increasing reliability for the dbt Semantic Layer and MetricFlow. Here are the updates and fixes for December 2023. ## Bug fixes -- The dbt Semantic Layer integration with Tableau now supports using exclude in its user interface. Previously it wasn’t supported. +- The dbt Semantic Layer integration with Tableau now supports queries that resolve to a "NOT IN" clause (for example: using "exclude" in the filtering user interface). Previously it wasn’t supported. - The dbt Semantic Layer can support `BIGINT` with over 18 digits. Previously it would return an error. -- The [dbt converter tool](https://github.com/dbt-labs/dbt-converter) can now convert data definitions from LookML to MetricFlow and help users upgrade. Previously this wasn’t available. (converts from lookml to metricflow specs). ROXI TO CLARIFY WITH NICK TO DETERMINE IF WE WANT TO TALK ABOUT THIS NOW OR LATER ON WHEN IT HAS MORE FEATURES. +- We fixed a memory leak that would amount in intermittent errors when querying our JDBC API. ## Improvements - dbt Labs deprecated [dbt Metrics and the legacy dbt Semantic Layer](/docs/dbt-versions/release-notes/Dec-2023/legacy-sl), both supported on dbt version 1.5 or lower. This change came into effect on December 15th, 2023. +- The [dbt converter tool](https://github.com/dbt-labs/dbt-converter) can now help automate some of the work in converting from LookML (Looker's modeling language) for those who are migrating. Previously this wasn’t available. ## New features - Test From 6edcf6509865a31359a6a4590d76adbdf9390f9c Mon Sep 17 00:00:00 2001 From: rpourzand Date: Mon, 18 Dec 2023 12:55:02 -0800 Subject: [PATCH 04/20] Update dec-sl-updates.md Diego recommendation --- .../dbt-versions/release-notes/74-Dec-2023/dec-sl-updates.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/docs/dbt-versions/release-notes/74-Dec-2023/dec-sl-updates.md b/website/docs/docs/dbt-versions/release-notes/74-Dec-2023/dec-sl-updates.md index cfdc8dd8b69..6757a59b86d 100644 --- a/website/docs/docs/dbt-versions/release-notes/74-Dec-2023/dec-sl-updates.md +++ b/website/docs/docs/dbt-versions/release-notes/74-Dec-2023/dec-sl-updates.md @@ -9,7 +9,7 @@ The dbt Labs team continues to work on adding new features, fixing bugs, and inc ## Bug fixes - The dbt Semantic Layer integration with Tableau now supports queries that resolve to a "NOT IN" clause (for example: using "exclude" in the filtering user interface). Previously it wasn’t supported. -- The dbt Semantic Layer can support `BIGINT` with over 18 digits. Previously it would return an error. +- The dbt Semantic Layer can support `BIGINT` with precision greater than 18. Previously it would return an error. - We fixed a memory leak that would amount in intermittent errors when querying our JDBC API. ## Improvements From 2eadd7126b895110bd816849d8f85b36850ae29d Mon Sep 17 00:00:00 2001 From: rpourzand Date: Mon, 18 Dec 2023 12:57:42 -0800 Subject: [PATCH 05/20] Update dec-sl-updates.md more recommendations from diego --- .../dbt-versions/release-notes/74-Dec-2023/dec-sl-updates.md | 1 + 1 file changed, 1 insertion(+) diff --git a/website/docs/docs/dbt-versions/release-notes/74-Dec-2023/dec-sl-updates.md b/website/docs/docs/dbt-versions/release-notes/74-Dec-2023/dec-sl-updates.md index 6757a59b86d..8f0bdd593c7 100644 --- a/website/docs/docs/dbt-versions/release-notes/74-Dec-2023/dec-sl-updates.md +++ b/website/docs/docs/dbt-versions/release-notes/74-Dec-2023/dec-sl-updates.md @@ -11,6 +11,7 @@ The dbt Labs team continues to work on adding new features, fixing bugs, and inc - The dbt Semantic Layer integration with Tableau now supports queries that resolve to a "NOT IN" clause (for example: using "exclude" in the filtering user interface). Previously it wasn’t supported. - The dbt Semantic Layer can support `BIGINT` with precision greater than 18. Previously it would return an error. - We fixed a memory leak that would amount in intermittent errors when querying our JDBC API. +- Added support for converting various Redshift and Postgres specific data types. Previously, the driver would throw an error when encountering columns with those types. ## Improvements - dbt Labs deprecated [dbt Metrics and the legacy dbt Semantic Layer](/docs/dbt-versions/release-notes/Dec-2023/legacy-sl), both supported on dbt version 1.5 or lower. This change came into effect on December 15th, 2023. From eb27064c4d942eb8266aebffcf03586fafbb546e Mon Sep 17 00:00:00 2001 From: Jordan Stein Date: Tue, 19 Dec 2023 14:15:28 -0800 Subject: [PATCH 06/20] add mf bug fixes and ambigous resolution --- .../release-notes/74-Dec-2023/dec-sl-updates.md | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/website/docs/docs/dbt-versions/release-notes/74-Dec-2023/dec-sl-updates.md b/website/docs/docs/dbt-versions/release-notes/74-Dec-2023/dec-sl-updates.md index 8f0bdd593c7..cc40dd88461 100644 --- a/website/docs/docs/dbt-versions/release-notes/74-Dec-2023/dec-sl-updates.md +++ b/website/docs/docs/dbt-versions/release-notes/74-Dec-2023/dec-sl-updates.md @@ -12,10 +12,19 @@ The dbt Labs team continues to work on adding new features, fixing bugs, and inc - The dbt Semantic Layer can support `BIGINT` with precision greater than 18. Previously it would return an error. - We fixed a memory leak that would amount in intermittent errors when querying our JDBC API. - Added support for converting various Redshift and Postgres specific data types. Previously, the driver would throw an error when encountering columns with those types. +- Apply time offset for nested dervied & ratio metrics ([#882](https://github.com/dbt-labs/metricflow/issues/882)) +- Fix Incorrect SQL Column Name Rendering for WhereConstraintNode ([#908](https://github.com/dbt-labs/metricflow/issues/908)) +- `Unable To Satisfy Query Error` with Cumulative Metrics in Saved Queries ([#917](https://github.com/dbt-labs/metricflow/issues/917)) +- Fixes a bug in dimension-only queries where the filter column is removed before the filter has been applied. ([#923](https://github.com/dbt-labs/metricflow/issues/923)) +- Bug fix: Keep where constraint column until used for nested derived offset metric queries. ([#930](https://github.com/dbt-labs/metricflow/issues/930)) ## Improvements - dbt Labs deprecated [dbt Metrics and the legacy dbt Semantic Layer](/docs/dbt-versions/release-notes/Dec-2023/legacy-sl), both supported on dbt version 1.5 or lower. This change came into effect on December 15th, 2023. - The [dbt converter tool](https://github.com/dbt-labs/dbt-converter) can now help automate some of the work in converting from LookML (Looker's modeling language) for those who are migrating. Previously this wasn’t available. ## New features -- Test +- Support for ambiguous group-by-item resolution. Previously, group-by-items were input by the user in a relatively specific form. For example, the group-by-item: +``` +guest__listing__created_at__month +``` +refers to the created_at time dimension at a month grain that is resolved by joining the measure source to the dimension sources by the guest and listing entities. Now we handle this complexity for the user, and allow you to simply request ``listing__created_at__month``. If there is only one possible resolution, we will resolve it for the user. If there are multiple possible resolutions, we will ask for additional user input. From 47b0043dee4eca006013bd080603cc6e0fef4ccd Mon Sep 17 00:00:00 2001 From: mirnawong1 Date: Wed, 20 Dec 2023 14:52:21 -0500 Subject: [PATCH 07/20] tweaks --- .../74-Dec-2023/dec-sl-updates.md | 52 +++++++++++-------- 1 file changed, 31 insertions(+), 21 deletions(-) diff --git a/website/docs/docs/dbt-versions/release-notes/74-Dec-2023/dec-sl-updates.md b/website/docs/docs/dbt-versions/release-notes/74-Dec-2023/dec-sl-updates.md index cc40dd88461..605683ed4c4 100644 --- a/website/docs/docs/dbt-versions/release-notes/74-Dec-2023/dec-sl-updates.md +++ b/website/docs/docs/dbt-versions/release-notes/74-Dec-2023/dec-sl-updates.md @@ -1,30 +1,40 @@ --- -title: "Updates and fixes: dbt Semantic Layer and MetricFlow updates for December 2023." +title: "dbt Semantic Layer and MetricFlow updates for December 2023" description: "December 2023: Enhanced Tableau integration, BIGINT support, LookML to MetricFlow conversion, and deprecation of legacy features." -sidebar_label: "Update ad fixes: dbt Semantic Layer and MetricFlow." +sidebar_label: "Update ad fixes: dbt Semantic Layer and MetricFlow" sidebar_position: 08 date: 2023-12-22 --- -The dbt Labs team continues to work on adding new features, fixing bugs, and increasing reliability for the dbt Semantic Layer and MetricFlow. Here are the updates and fixes for December 2023. - -## Bug fixes -- The dbt Semantic Layer integration with Tableau now supports queries that resolve to a "NOT IN" clause (for example: using "exclude" in the filtering user interface). Previously it wasn’t supported. -- The dbt Semantic Layer can support `BIGINT` with precision greater than 18. Previously it would return an error. -- We fixed a memory leak that would amount in intermittent errors when querying our JDBC API. -- Added support for converting various Redshift and Postgres specific data types. Previously, the driver would throw an error when encountering columns with those types. -- Apply time offset for nested dervied & ratio metrics ([#882](https://github.com/dbt-labs/metricflow/issues/882)) -- Fix Incorrect SQL Column Name Rendering for WhereConstraintNode ([#908](https://github.com/dbt-labs/metricflow/issues/908)) -- `Unable To Satisfy Query Error` with Cumulative Metrics in Saved Queries ([#917](https://github.com/dbt-labs/metricflow/issues/917)) -- Fixes a bug in dimension-only queries where the filter column is removed before the filter has been applied. ([#923](https://github.com/dbt-labs/metricflow/issues/923)) -- Bug fix: Keep where constraint column until used for nested derived offset metric queries. ([#930](https://github.com/dbt-labs/metricflow/issues/930)) +The dbt Labs team continues to work on adding new features, fixing bugs, and increasing reliability for the dbt Semantic Layer and MetricFlow. + +Refer to the following updates and fixes for December 2023: + +## gBug fixes + +The following are fixes for the dbt Semantic Layer and MetricFlow: + +**dbt Semantic Layer** + +- Tableau integration — The dbt Semantic Layer integration with Tableau now supports queries that resolve to a "NOT IN" clause. This applies to using "exclude" in the filtering user interface. Previously it wasn’t supported. +- `BIGINT` support — The dbt Semantic Layer can now support `BIGINT` values with precision greater than 18. Previously it would return an error. +- Memory leak — We fixed a memory leak in the JDBC API that would previously lead to intermittent errors when querying it. +- Data conversion support — Added support for converting various Redshift and Postgres-specific data types. Previously, the driver would throw an error when encountering columns with those types. + +**MetricFlow** + +- Time offset for nested metrics — Implemented time offset for nested derived and ratio metrics. ([MetricFlow Issue #882](https://github.com/dbt-labs/metricflow/issues/882)) +- SQL column name rendering: — Fixed incorrect SQL column name rendering in `WhereConstraintNode`. ([MetricFlow Issue #908](https://github.com/dbt-labs/metricflow/issues/908)) +- Cumulative metrics query error — Fixed the `Unable To Satisfy Query` error with cumulative metrics in Saved Queries. ([MetricFlow Issue #917](https://github.com/dbt-labs/metricflow/issues/917)) +- Dimension-only query — Fixes a bug in dimension-only queries where the filter column is removed before the filter has been applied. ([MetricFlow Issue #923](https://github.com/dbt-labs/metricflow/issues/923)) +- Where constraint column — Ensured retention of the where constraint column until used for nested derived offset metric queries. ([MetricFlow Issue #930](https://github.com/dbt-labs/metricflow/issues/930)) ## Improvements -- dbt Labs deprecated [dbt Metrics and the legacy dbt Semantic Layer](/docs/dbt-versions/release-notes/Dec-2023/legacy-sl), both supported on dbt version 1.5 or lower. This change came into effect on December 15th, 2023. -- The [dbt converter tool](https://github.com/dbt-labs/dbt-converter) can now help automate some of the work in converting from LookML (Looker's modeling language) for those who are migrating. Previously this wasn’t available. + +- Deprecation — We deprecated [dbt Metrics and the legacy dbt Semantic Layer](/docs/dbt-versions/release-notes/Dec-2023/legacy-sl), both supported on dbt version 1.5 or lower. This change came into effect on December 15th, 2023. +- Improved dbt converter tool — The [dbt converter tool](https://github.com/dbt-labs/dbt-converter) can now help automate some of the work in converting from LookML (Looker's modeling language) for those who are migrating. Previously this wasn’t available. ## New features -- Support for ambiguous group-by-item resolution. Previously, group-by-items were input by the user in a relatively specific form. For example, the group-by-item: -``` -guest__listing__created_at__month -``` -refers to the created_at time dimension at a month grain that is resolved by joining the measure source to the dimension sources by the guest and listing entities. Now we handle this complexity for the user, and allow you to simply request ``listing__created_at__month``. If there is only one possible resolution, we will resolve it for the user. If there are multiple possible resolutions, we will ask for additional user input. + +- Simplified group-by-item requests — Improved support for ambiguous group-by-item resolution. Previously, you need to specify them in detail, like `guest__listing__created_at__month`. This indicates a monthly `created_at` time dimension, linked by `guest` and `listing` entities. + + Now you can use a shorter form, like ` listing__created_at__month`. If there's only one way to interpret this, dbt will resolve it automatically. If multiple interpretations are possible, dbt will ask for more details from the user. From 92ac11846dbadb4642bf5e510a8f14339b55fea7 Mon Sep 17 00:00:00 2001 From: mirnawong1 Date: Wed, 20 Dec 2023 14:53:34 -0500 Subject: [PATCH 08/20] consistent language --- .../release-notes/74-Dec-2023/dec-sl-updates.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/website/docs/docs/dbt-versions/release-notes/74-Dec-2023/dec-sl-updates.md b/website/docs/docs/dbt-versions/release-notes/74-Dec-2023/dec-sl-updates.md index 605683ed4c4..6895dce1f1a 100644 --- a/website/docs/docs/dbt-versions/release-notes/74-Dec-2023/dec-sl-updates.md +++ b/website/docs/docs/dbt-versions/release-notes/74-Dec-2023/dec-sl-updates.md @@ -9,7 +9,7 @@ The dbt Labs team continues to work on adding new features, fixing bugs, and inc Refer to the following updates and fixes for December 2023: -## gBug fixes +## Bug fixes The following are fixes for the dbt Semantic Layer and MetricFlow: @@ -17,7 +17,7 @@ The following are fixes for the dbt Semantic Layer and MetricFlow: - Tableau integration — The dbt Semantic Layer integration with Tableau now supports queries that resolve to a "NOT IN" clause. This applies to using "exclude" in the filtering user interface. Previously it wasn’t supported. - `BIGINT` support — The dbt Semantic Layer can now support `BIGINT` values with precision greater than 18. Previously it would return an error. -- Memory leak — We fixed a memory leak in the JDBC API that would previously lead to intermittent errors when querying it. +- Memory leak — Fixed a memory leak in the JDBC API that would previously lead to intermittent errors when querying it. - Data conversion support — Added support for converting various Redshift and Postgres-specific data types. Previously, the driver would throw an error when encountering columns with those types. **MetricFlow** @@ -25,7 +25,7 @@ The following are fixes for the dbt Semantic Layer and MetricFlow: - Time offset for nested metrics — Implemented time offset for nested derived and ratio metrics. ([MetricFlow Issue #882](https://github.com/dbt-labs/metricflow/issues/882)) - SQL column name rendering: — Fixed incorrect SQL column name rendering in `WhereConstraintNode`. ([MetricFlow Issue #908](https://github.com/dbt-labs/metricflow/issues/908)) - Cumulative metrics query error — Fixed the `Unable To Satisfy Query` error with cumulative metrics in Saved Queries. ([MetricFlow Issue #917](https://github.com/dbt-labs/metricflow/issues/917)) -- Dimension-only query — Fixes a bug in dimension-only queries where the filter column is removed before the filter has been applied. ([MetricFlow Issue #923](https://github.com/dbt-labs/metricflow/issues/923)) +- Dimension-only query — Fixed a bug in dimension-only queries where the filter column is removed before the filter has been applied. ([MetricFlow Issue #923](https://github.com/dbt-labs/metricflow/issues/923)) - Where constraint column — Ensured retention of the where constraint column until used for nested derived offset metric queries. ([MetricFlow Issue #930](https://github.com/dbt-labs/metricflow/issues/930)) ## Improvements From 89aeae466e9b3cad71ce85cbc1ec4672663c4be8 Mon Sep 17 00:00:00 2001 From: mirnawong1 Date: Wed, 20 Dec 2023 14:54:31 -0500 Subject: [PATCH 09/20] typo --- .../dbt-versions/release-notes/74-Dec-2023/dec-sl-updates.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/docs/dbt-versions/release-notes/74-Dec-2023/dec-sl-updates.md b/website/docs/docs/dbt-versions/release-notes/74-Dec-2023/dec-sl-updates.md index 6895dce1f1a..8fce5b837c7 100644 --- a/website/docs/docs/dbt-versions/release-notes/74-Dec-2023/dec-sl-updates.md +++ b/website/docs/docs/dbt-versions/release-notes/74-Dec-2023/dec-sl-updates.md @@ -1,7 +1,7 @@ --- title: "dbt Semantic Layer and MetricFlow updates for December 2023" description: "December 2023: Enhanced Tableau integration, BIGINT support, LookML to MetricFlow conversion, and deprecation of legacy features." -sidebar_label: "Update ad fixes: dbt Semantic Layer and MetricFlow" +sidebar_label: "Update and fixes: dbt Semantic Layer and MetricFlow" sidebar_position: 08 date: 2023-12-22 --- From 27cd55515fa34e88666ce3e1290fd89cd7708818 Mon Sep 17 00:00:00 2001 From: mirnawong1 Date: Wed, 20 Dec 2023 14:56:13 -0500 Subject: [PATCH 10/20] tweak --- .../dbt-versions/release-notes/74-Dec-2023/dec-sl-updates.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/docs/dbt-versions/release-notes/74-Dec-2023/dec-sl-updates.md b/website/docs/docs/dbt-versions/release-notes/74-Dec-2023/dec-sl-updates.md index 8fce5b837c7..96a1e20fc6b 100644 --- a/website/docs/docs/dbt-versions/release-notes/74-Dec-2023/dec-sl-updates.md +++ b/website/docs/docs/dbt-versions/release-notes/74-Dec-2023/dec-sl-updates.md @@ -11,7 +11,7 @@ Refer to the following updates and fixes for December 2023: ## Bug fixes -The following are fixes for the dbt Semantic Layer and MetricFlow: +The following are updates for the dbt Semantic Layer and MetricFlow: **dbt Semantic Layer** From 7f5890dc973e090483b92f9d95646d90541e4309 Mon Sep 17 00:00:00 2001 From: Jordan Stein Date: Wed, 20 Dec 2023 16:40:01 -0800 Subject: [PATCH 11/20] update group by items call out --- .../dbt-versions/release-notes/74-Dec-2023/dec-sl-updates.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/website/docs/docs/dbt-versions/release-notes/74-Dec-2023/dec-sl-updates.md b/website/docs/docs/dbt-versions/release-notes/74-Dec-2023/dec-sl-updates.md index 96a1e20fc6b..1b01a93fefd 100644 --- a/website/docs/docs/dbt-versions/release-notes/74-Dec-2023/dec-sl-updates.md +++ b/website/docs/docs/dbt-versions/release-notes/74-Dec-2023/dec-sl-updates.md @@ -35,6 +35,7 @@ The following are updates for the dbt Semantic Layer and MetricFlow: ## New features -- Simplified group-by-item requests — Improved support for ambiguous group-by-item resolution. Previously, you need to specify them in detail, like `guest__listing__created_at__month`. This indicates a monthly `created_at` time dimension, linked by `guest` and `listing` entities. +- Simplified group-by-item requests. We updated the way the MetricFlow query resolver finds queryable dimensions for metrics. The main improvements ares: + - If the grain of a time dimension in a query is not specified, then the grain of the requested time dimension is resolved to be the finest grain that is available for the queried metrics. For example, say you have two metrics; revenue which has a weekly grain and orders which has a daily grain. If you query these metrics like this: `dbt sl query --metrics revenue,orders --group-by metric_time` metricflow will automatically query these metrics at a weekly grain. - Now you can use a shorter form, like ` listing__created_at__month`. If there's only one way to interpret this, dbt will resolve it automatically. If multiple interpretations are possible, dbt will ask for more details from the user. +- In a metric filter, if an ambiguous time dimension does not specify the grain, and all semantic models that are used to compute the metric define the time dimension with the same grain, MetricFlow should assume the specific time dimension is that grain. For example, say I have two metrics; revenue and users which are both daily. I can query these metrics without sepcifying the time dimension grain in the filte i.e `mf query --metrics users,revenue --group-by metric_time --where "{{ TimeDimension('metric_time') }} = '2017-07-30' "` From b839ea5b9c749300db47d14460a912e43860ea99 Mon Sep 17 00:00:00 2001 From: mirnawong1 <89008547+mirnawong1@users.noreply.github.com> Date: Thu, 21 Dec 2023 15:49:54 -0500 Subject: [PATCH 12/20] Update website/docs/docs/dbt-versions/release-notes/74-Dec-2023/dec-sl-updates.md --- .../dbt-versions/release-notes/74-Dec-2023/dec-sl-updates.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/website/docs/docs/dbt-versions/release-notes/74-Dec-2023/dec-sl-updates.md b/website/docs/docs/dbt-versions/release-notes/74-Dec-2023/dec-sl-updates.md index 1b01a93fefd..dbdf66c8e64 100644 --- a/website/docs/docs/dbt-versions/release-notes/74-Dec-2023/dec-sl-updates.md +++ b/website/docs/docs/dbt-versions/release-notes/74-Dec-2023/dec-sl-updates.md @@ -38,4 +38,6 @@ The following are updates for the dbt Semantic Layer and MetricFlow: - Simplified group-by-item requests. We updated the way the MetricFlow query resolver finds queryable dimensions for metrics. The main improvements ares: - If the grain of a time dimension in a query is not specified, then the grain of the requested time dimension is resolved to be the finest grain that is available for the queried metrics. For example, say you have two metrics; revenue which has a weekly grain and orders which has a daily grain. If you query these metrics like this: `dbt sl query --metrics revenue,orders --group-by metric_time` metricflow will automatically query these metrics at a weekly grain. -- In a metric filter, if an ambiguous time dimension does not specify the grain, and all semantic models that are used to compute the metric define the time dimension with the same grain, MetricFlow should assume the specific time dimension is that grain. For example, say I have two metrics; revenue and users which are both daily. I can query these metrics without sepcifying the time dimension grain in the filte i.e `mf query --metrics users,revenue --group-by metric_time --where "{{ TimeDimension('metric_time') }} = '2017-07-30' "` +- Assumes time dimension grain: When using a metric filter, if an ambiguous time dimension doesn't specify the grain, and all used semantic models define this time dimension with the same grain, MetricFlow now automatically assumes the time dimension to be of that grain. + - For example, if you have two daily metrics: `revenue` and `users` — you can now query these metrics without specifying the time dimension grain in the filter: `mf query --metrics users,revenue --group-by metric_time --where "{{ TimeDimension('metric_time') }} = '2017-07-30' "` + From 224ce876c19ffb86a0826c004fda0a2c2b79e2cf Mon Sep 17 00:00:00 2001 From: mirnawong1 <89008547+mirnawong1@users.noreply.github.com> Date: Thu, 21 Dec 2023 15:53:40 -0500 Subject: [PATCH 13/20] Update website/docs/docs/dbt-versions/release-notes/74-Dec-2023/dec-sl-updates.md --- .../dbt-versions/release-notes/74-Dec-2023/dec-sl-updates.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/docs/dbt-versions/release-notes/74-Dec-2023/dec-sl-updates.md b/website/docs/docs/dbt-versions/release-notes/74-Dec-2023/dec-sl-updates.md index dbdf66c8e64..be8e5e8e61f 100644 --- a/website/docs/docs/dbt-versions/release-notes/74-Dec-2023/dec-sl-updates.md +++ b/website/docs/docs/dbt-versions/release-notes/74-Dec-2023/dec-sl-updates.md @@ -7,7 +7,7 @@ date: 2023-12-22 --- The dbt Labs team continues to work on adding new features, fixing bugs, and increasing reliability for the dbt Semantic Layer and MetricFlow. -Refer to the following updates and fixes for December 2023: +Refer to the following updates and fixes for December 2023. ## Bug fixes From b75662226b7b48c64cfac86169173aab5b72329e Mon Sep 17 00:00:00 2001 From: Jordan Stein Date: Thu, 21 Dec 2023 13:40:35 -0800 Subject: [PATCH 14/20] update release notes --- .../release-notes/74-Dec-2023/dec-sl-updates.md | 17 +---------------- 1 file changed, 1 insertion(+), 16 deletions(-) diff --git a/website/docs/docs/dbt-versions/release-notes/74-Dec-2023/dec-sl-updates.md b/website/docs/docs/dbt-versions/release-notes/74-Dec-2023/dec-sl-updates.md index be8e5e8e61f..7491d17c039 100644 --- a/website/docs/docs/dbt-versions/release-notes/74-Dec-2023/dec-sl-updates.md +++ b/website/docs/docs/dbt-versions/release-notes/74-Dec-2023/dec-sl-updates.md @@ -7,7 +7,7 @@ date: 2023-12-22 --- The dbt Labs team continues to work on adding new features, fixing bugs, and increasing reliability for the dbt Semantic Layer and MetricFlow. -Refer to the following updates and fixes for December 2023. +Refer to the following updates and fixes for December 2023: ## Bug fixes @@ -20,24 +20,9 @@ The following are updates for the dbt Semantic Layer and MetricFlow: - Memory leak — Fixed a memory leak in the JDBC API that would previously lead to intermittent errors when querying it. - Data conversion support — Added support for converting various Redshift and Postgres-specific data types. Previously, the driver would throw an error when encountering columns with those types. -**MetricFlow** - -- Time offset for nested metrics — Implemented time offset for nested derived and ratio metrics. ([MetricFlow Issue #882](https://github.com/dbt-labs/metricflow/issues/882)) -- SQL column name rendering: — Fixed incorrect SQL column name rendering in `WhereConstraintNode`. ([MetricFlow Issue #908](https://github.com/dbt-labs/metricflow/issues/908)) -- Cumulative metrics query error — Fixed the `Unable To Satisfy Query` error with cumulative metrics in Saved Queries. ([MetricFlow Issue #917](https://github.com/dbt-labs/metricflow/issues/917)) -- Dimension-only query — Fixed a bug in dimension-only queries where the filter column is removed before the filter has been applied. ([MetricFlow Issue #923](https://github.com/dbt-labs/metricflow/issues/923)) -- Where constraint column — Ensured retention of the where constraint column until used for nested derived offset metric queries. ([MetricFlow Issue #930](https://github.com/dbt-labs/metricflow/issues/930)) ## Improvements - Deprecation — We deprecated [dbt Metrics and the legacy dbt Semantic Layer](/docs/dbt-versions/release-notes/Dec-2023/legacy-sl), both supported on dbt version 1.5 or lower. This change came into effect on December 15th, 2023. - Improved dbt converter tool — The [dbt converter tool](https://github.com/dbt-labs/dbt-converter) can now help automate some of the work in converting from LookML (Looker's modeling language) for those who are migrating. Previously this wasn’t available. -## New features - -- Simplified group-by-item requests. We updated the way the MetricFlow query resolver finds queryable dimensions for metrics. The main improvements ares: - - If the grain of a time dimension in a query is not specified, then the grain of the requested time dimension is resolved to be the finest grain that is available for the queried metrics. For example, say you have two metrics; revenue which has a weekly grain and orders which has a daily grain. If you query these metrics like this: `dbt sl query --metrics revenue,orders --group-by metric_time` metricflow will automatically query these metrics at a weekly grain. - -- Assumes time dimension grain: When using a metric filter, if an ambiguous time dimension doesn't specify the grain, and all used semantic models define this time dimension with the same grain, MetricFlow now automatically assumes the time dimension to be of that grain. - - For example, if you have two daily metrics: `revenue` and `users` — you can now query these metrics without specifying the time dimension grain in the filter: `mf query --metrics users,revenue --group-by metric_time --where "{{ TimeDimension('metric_time') }} = '2017-07-30' "` - From 03ec70050b076a4cbcb3c58690b1c6b247129328 Mon Sep 17 00:00:00 2001 From: mirnawong1 <89008547+mirnawong1@users.noreply.github.com> Date: Thu, 21 Dec 2023 16:49:37 -0500 Subject: [PATCH 15/20] Update website/docs/docs/dbt-versions/release-notes/74-Dec-2023/dec-sl-updates.md --- .../dbt-versions/release-notes/74-Dec-2023/dec-sl-updates.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/docs/dbt-versions/release-notes/74-Dec-2023/dec-sl-updates.md b/website/docs/docs/dbt-versions/release-notes/74-Dec-2023/dec-sl-updates.md index 7491d17c039..598908dc921 100644 --- a/website/docs/docs/dbt-versions/release-notes/74-Dec-2023/dec-sl-updates.md +++ b/website/docs/docs/dbt-versions/release-notes/74-Dec-2023/dec-sl-updates.md @@ -1,5 +1,5 @@ --- -title: "dbt Semantic Layer and MetricFlow updates for December 2023" +title: "dbt Semantic Layer updates for December 2023" description: "December 2023: Enhanced Tableau integration, BIGINT support, LookML to MetricFlow conversion, and deprecation of legacy features." sidebar_label: "Update and fixes: dbt Semantic Layer and MetricFlow" sidebar_position: 08 From 31339d2dbd19d93d33a552691b6187812fdb3174 Mon Sep 17 00:00:00 2001 From: mirnawong1 <89008547+mirnawong1@users.noreply.github.com> Date: Thu, 21 Dec 2023 16:49:52 -0500 Subject: [PATCH 16/20] Update website/docs/docs/dbt-versions/release-notes/74-Dec-2023/dec-sl-updates.md --- .../dbt-versions/release-notes/74-Dec-2023/dec-sl-updates.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/docs/dbt-versions/release-notes/74-Dec-2023/dec-sl-updates.md b/website/docs/docs/dbt-versions/release-notes/74-Dec-2023/dec-sl-updates.md index 598908dc921..63ecd37fb4b 100644 --- a/website/docs/docs/dbt-versions/release-notes/74-Dec-2023/dec-sl-updates.md +++ b/website/docs/docs/dbt-versions/release-notes/74-Dec-2023/dec-sl-updates.md @@ -1,7 +1,7 @@ --- title: "dbt Semantic Layer updates for December 2023" description: "December 2023: Enhanced Tableau integration, BIGINT support, LookML to MetricFlow conversion, and deprecation of legacy features." -sidebar_label: "Update and fixes: dbt Semantic Layer and MetricFlow" +sidebar_label: "Update and fixes: dbt Semantic Layer" sidebar_position: 08 date: 2023-12-22 --- From 4f9e6c061010edf298a1eb631a0779ebb0b6e961 Mon Sep 17 00:00:00 2001 From: mirnawong1 <89008547+mirnawong1@users.noreply.github.com> Date: Thu, 21 Dec 2023 16:50:04 -0500 Subject: [PATCH 17/20] Update website/docs/docs/dbt-versions/release-notes/74-Dec-2023/dec-sl-updates.md --- .../dbt-versions/release-notes/74-Dec-2023/dec-sl-updates.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/docs/dbt-versions/release-notes/74-Dec-2023/dec-sl-updates.md b/website/docs/docs/dbt-versions/release-notes/74-Dec-2023/dec-sl-updates.md index 63ecd37fb4b..7213962b58f 100644 --- a/website/docs/docs/dbt-versions/release-notes/74-Dec-2023/dec-sl-updates.md +++ b/website/docs/docs/dbt-versions/release-notes/74-Dec-2023/dec-sl-updates.md @@ -5,7 +5,7 @@ sidebar_label: "Update and fixes: dbt Semantic Layer" sidebar_position: 08 date: 2023-12-22 --- -The dbt Labs team continues to work on adding new features, fixing bugs, and increasing reliability for the dbt Semantic Layer and MetricFlow. +The dbt Labs team continues to work on adding new features, fixing bugs, and increasing reliability for the dbt Semantic Layer. Refer to the following updates and fixes for December 2023: From 2811e4353e0d1a25e00f4c99a6f5616b7d4c3ebb Mon Sep 17 00:00:00 2001 From: mirnawong1 <89008547+mirnawong1@users.noreply.github.com> Date: Thu, 21 Dec 2023 16:50:16 -0500 Subject: [PATCH 18/20] Update website/docs/docs/dbt-versions/release-notes/74-Dec-2023/dec-sl-updates.md --- .../dbt-versions/release-notes/74-Dec-2023/dec-sl-updates.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/docs/dbt-versions/release-notes/74-Dec-2023/dec-sl-updates.md b/website/docs/docs/dbt-versions/release-notes/74-Dec-2023/dec-sl-updates.md index 7213962b58f..7bb44b44724 100644 --- a/website/docs/docs/dbt-versions/release-notes/74-Dec-2023/dec-sl-updates.md +++ b/website/docs/docs/dbt-versions/release-notes/74-Dec-2023/dec-sl-updates.md @@ -11,7 +11,7 @@ Refer to the following updates and fixes for December 2023: ## Bug fixes -The following are updates for the dbt Semantic Layer and MetricFlow: +The following are updates for the dbt Semantic Layer: **dbt Semantic Layer** From 13d1fcf10cbf7c81218a6fafaf7f11b146c25616 Mon Sep 17 00:00:00 2001 From: Amy Chen Date: Fri, 22 Dec 2023 09:18:07 -0500 Subject: [PATCH 19/20] update author --- website/blog/authors.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/blog/authors.yml b/website/blog/authors.yml index 82cc300bdc8..a3548575b6e 100644 --- a/website/blog/authors.yml +++ b/website/blog/authors.yml @@ -1,6 +1,6 @@ amy_chen: image_url: /img/blog/authors/achen.png - job_title: Product Partnerships Manager + job_title: Product Ecosystem Manager links: - icon: fa-linkedin url: https://www.linkedin.com/in/yuanamychen/ From cc0ca46db3c792b9ecc5bdab96b380214eeba4cb Mon Sep 17 00:00:00 2001 From: mirnawong1 <89008547+mirnawong1@users.noreply.github.com> Date: Fri, 22 Dec 2023 09:34:15 -0500 Subject: [PATCH 20/20] Update dec-sl-updates.md --- .../release-notes/74-Dec-2023/dec-sl-updates.md | 8 +------- 1 file changed, 1 insertion(+), 7 deletions(-) diff --git a/website/docs/docs/dbt-versions/release-notes/74-Dec-2023/dec-sl-updates.md b/website/docs/docs/dbt-versions/release-notes/74-Dec-2023/dec-sl-updates.md index 7bb44b44724..401b43fb333 100644 --- a/website/docs/docs/dbt-versions/release-notes/74-Dec-2023/dec-sl-updates.md +++ b/website/docs/docs/dbt-versions/release-notes/74-Dec-2023/dec-sl-updates.md @@ -5,16 +5,10 @@ sidebar_label: "Update and fixes: dbt Semantic Layer" sidebar_position: 08 date: 2023-12-22 --- -The dbt Labs team continues to work on adding new features, fixing bugs, and increasing reliability for the dbt Semantic Layer. - -Refer to the following updates and fixes for December 2023: +The dbt Labs team continues to work on adding new features, fixing bugs, and increasing reliability for the dbt Semantic Layer. The following list explains the updates and fixes for December 2023 in more detail. ## Bug fixes -The following are updates for the dbt Semantic Layer: - -**dbt Semantic Layer** - - Tableau integration — The dbt Semantic Layer integration with Tableau now supports queries that resolve to a "NOT IN" clause. This applies to using "exclude" in the filtering user interface. Previously it wasn’t supported. - `BIGINT` support — The dbt Semantic Layer can now support `BIGINT` values with precision greater than 18. Previously it would return an error. - Memory leak — Fixed a memory leak in the JDBC API that would previously lead to intermittent errors when querying it.