clariy multihop depth #4973
Merged
clariy multihop depth #4973
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
this pr clarifies multi-hop depth and whether more than 3 joins are supported in mf. stemmed from users asking and this slack thread: https://dbt-labs.slack.com/archives/C03KHQRQUBX/p1708571327378159?thread_ts=1708570486.187929&cid=C03KHQRQUBX
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
github-actions
bot
added
content
mirnawong1
commented
Feb 28, 2024
|
|
||
| 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. | ||
| MetricFlow can join up to three tables, supporting multi-hop joins with a limit of two hops. This enables complex data analysis without ambiguous paths. It supports navigating through data models, like moving from `orders` to `customers` to `country` tables. While direct three-hop paths are limited to prevent confusion from multiple routes to the same data, MetricFlow does allow joining more than three tables if the joins don’t exceed two hops to reach a dimension. |
There was a problem hiding this comment.
hey @Jstein77 - does this sound right?
| MetricFlow can join up to three tables, supporting multi-hop joins with a limit of two hops. This does the following: | ||
| - Enables complex data analysis without ambiguous paths. | ||
| - Supports navigating through data models, like moving from `orders` to `customers` to `country` tables. | ||
| - While direct three-hop paths are limited to prevent confusion from multiple routes to the same data, MetricFlow does allow joining more than three tables if the joins don’t exceed two hops to reach a dimension. |
There was a problem hiding this comment.
This last point feels a little out of place. Should it be a follow-up note or maybe reworded?
Reading aloud:
This does the following... enables ✅... supports✅... while direct...
add 3rd sm
Co-authored-by: Matt Shaver <[email protected]>
Co-authored-by: Matt Shaver <[email protected]>
mirnawong1
commented
Mar 13, 2024
matthewshaver
approved these changes
Mar 13, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
this pr clarifies multi-hop depth and whether more than 3 joins are supported in mf.
stemmed from users asking and this slack thread: https://dbt-labs.slack.com/archives/C03KHQRQUBX/p1708571327378159?thread_ts=1708570486.187929&cid=C03KHQRQUBX