Open sohai-max opened 2 months ago
Hi @sohai-max and thanks for reaching out!
Without any context, I just want to let you know, that we always recommend materializing all Raw Vault entities as "incremental" to ensure proper historization.
But coming back to your question, a clustering key for transient tables isn't really something we can implement with our package, instead it needs to be defined in the model config.
Check out the dbt documentation about the parameter "cluster_by" here.
Let me know if this helps!
Best regards Tim
Hi, is there a plan to optionally include a hashkey as a clustering key during the creation of transient tables? This could enhance query performance when joining large tables, although using business keys instead of hashkeys for joining can address this issue as well.