Currently only equality joins are available to define relationship between tables. Any complex joins have to be resolved in having different “bridge” tables which is an additional workstream for datateam + additional load for DWH to execute queries. Ideally, there should be an option to define custom joins (as in looker where you can write custom join condition)
Agreed - the equality join is one area that I’ve always thought was too simple in Holistics (although you can push that complexity upstream). Compare with Looker’s crazy joins (including many to many)!
Hi @Alex_H and @Datatech_Owner,
Thanks for sharing this feedback! We completely acknowledge your point here. Since Holistics relies on a relationship-based approach while Looker is join-based, the two platforms handle these complex scenarios quite differently.
We’d love to help you find the best path forward. Could you share the specific use case so that we can guide you on how to adapt and solve it cleanly using our modeling framework?