From 1f14e32df332d5fa66bb59ee2c977f5bbd013fb7 Mon Sep 17 00:00:00 2001 From: Jordan Stein Date: Tue, 19 Dec 2023 09:11:13 -0800 Subject: [PATCH 1/2] update join page with multi-hop limitation --- website/docs/docs/build/join-logic.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/website/docs/docs/build/join-logic.md b/website/docs/docs/build/join-logic.md index 29b9d101a59..e701fd1b012 100644 --- a/website/docs/docs/build/join-logic.md +++ b/website/docs/docs/build/join-logic.md @@ -84,6 +84,10 @@ mf query --metrics average_purchase_price --dimensions metric_time,user_id__type ## Multi-hop joins +:::info +MetricFlow currently supports multi-hop joins with up to two hops. This means we can render joins between three tables at most. +::: + MetricFlow allows users to join measures and dimensions across a graph of entities, which we refer to as a 'multi-hop join.' This is because users can move from one table to another like a 'hop' within a graph. Here's an example schema for reference: From 7eaa763500508ad0caf58db97d679883c6289294 Mon Sep 17 00:00:00 2001 From: Jordan Date: Tue, 19 Dec 2023 09:18:14 -0800 Subject: [PATCH 2/2] Update website/docs/docs/build/join-logic.md Co-authored-by: mirnawong1 <89008547+mirnawong1@users.noreply.github.com> --- website/docs/docs/build/join-logic.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/docs/build/join-logic.md b/website/docs/docs/build/join-logic.md index e701fd1b012..e2656692eee 100644 --- a/website/docs/docs/build/join-logic.md +++ b/website/docs/docs/build/join-logic.md @@ -85,7 +85,7 @@ mf query --metrics average_purchase_price --dimensions metric_time,user_id__type ## Multi-hop joins :::info -MetricFlow currently supports multi-hop joins with up to two hops. This means we can render joins between three tables at most. +MetricFlow can join three tables at most, supporting multi-hop joins with a limit of two hops. ::: MetricFlow allows users to join measures and dimensions across a graph of entities, which we refer to as a 'multi-hop join.' This is because users can move from one table to another like a 'hop' within a graph.