I’ve been thinking about ways to simplify logical model of LookML and one of the main issues that come to mind at first is the following:
Let’s assume we have views of our main enities of an imaginary online store:
users
countries
Then we have entities that represent events / actions:
orders
favourites
products
For orders we need multiple joins to get the attributes of the connected entities:
orders.buyer_id = users.id
orders.seller_id = users.id
orders.shop_country_id = countries.id
And there could be a lot more. Imagine your action-based views almost always have to join to 1-3 of those main views.
It’s just brainstorming at this stage as extends
change the base of your explore but I thought it could be interesting to talk about how people go about it.
To be honest it’s my OCD kicking in when I see the same JOINs in 25 places 😃