Skip to main content

dbt - more stuff

The more I used dbt the more I like it. I am finding many of its features really useful and I haven't even done the training on macros and packages yet so I feel there is more to come yet. In the meantime I have now start to, just of the fun of it, create some downstream views with dependencies on other steps and a function in SQL. Happy to say it is all working really well and using jinja (and my Snowflake function) has saved me heap of time coding. 

Sources yml: 

version: 2
sources:
- name: exercise_data
description: Source table from Snoflake
database: KEBOOLA_7127
schema: WORKSPACE_15661914
tables:
- name: EXERCISE_FACT
- name: V_EXERCISE_STAR
view raw source.yml hosted with ❤ by GitHub


View using the source function (results in SQL)

{%- set activities = ['Pull_Up', 'Crunch','Push_Up','Plank_Time','Dumbbells','Box_Jump'] -%}
select {% for activity in activities -%}
sum(case when replace(description,' ','_') = '{{ activity }}' then act_count else 0 end)
as {{ activity }}_count
{%- if not loop.last -%}
,
{% endif -%}
{%- endfor %}
from {{ source('exercise_data','V_EXERCISE_STAR') }}


View that references the output from previous steps, allows them to be linked: 

{{ config(materialized='view') }}
{%- set activities = ['Pull_Up_count', 'Crunch_count','Push_Up_count','Plank_Time_count','Dumbbells_count','Box_Jump_count'] -%}
select pf.*,
mf.*,
{% for activity in activities -%}
f_exercise_out({{ activity }},{{ activity }}_avg, {{ activity }}_sd , 1) as {{ activity }}_status
{%- if not loop.last -%}
,
{% endif -%}
{%- endfor %}
FROM
{{ ref('exercise_pivot_fact') }} pf
CROSS JOIN {{ ref('stg_total_metrics') }} mf
order by 1 desc


Assuming you create your sources in the yml file and reference previous steps using the reference function rather than calling the resulting table (dbt handles that for you) (as shown above) it will automatically work out the dependencies, run things in the right order and produces a lovely lineage graph like so. 



I am hoping to stop playing with what I know of dbt and might make some visuals based on the extra processing I have done before playing with dbt some more by working through some more of the training. 



Comments

Popular posts from this blog

Gen AI news 29-04-2024

Here are some recent updates and insights related to Generative AI (gen AI) : Enterprise Hits and Misses - Robotics and Gen AI Converge : This article discusses the convergence of robotics and generative AI. It explores breakthroughs needed in the field, the FTC’s policy change regarding non-competes, and the impact on AI model sizes for enterprises 1 . Read more All You Need To Know About The Upcoming AI-Powered OLED iPad Pro : This piece provides a summary of rumors surrounding the next-gen AI-fused OLED iPad Pro, powered by the new Apple M4 chip 2 . Read more Delivering on the Promise of Gen AI : New Electronics reflects on NVIDIA GTC and key announcements that contribute to delivering on the promises made for generative AI 3 . Read more The Future of Generative AI - An Early View in 15 Charts (McKinsey): Since the release of ChatGPT in November 2022, generative AI has been making headlines. McKinsey research estimates that gen AI features could add up to $4.4 trillion to the globa...

Keboola Flows

Really finding Keboola was the thing that kickstarted this project otherwise I would be trying to build custom code on a python cloud server and building everything from scratch.  In Keboola you build you data sources and destinations using connection details which is fairly simple and something I will likely cover in another post, same goes for transformations etc. Here though I am going to discuss Flows, this is where you bring everything together. On my free account there are some limitations.  My easiest flow is very basic:  Pull parkrun results e-mail from Gmail to Google Sheets (actually done by Zap not Keboola).  Keboola will, as often as I like, in this case once a week, pull the data from the sheet into its storage.  It will then transfer this to the target database. Currently I have this setup to be MySQL database but I can and might expand that to the Snowflake instance within Keboola.  I then, outside of Keboola, connect to the MySQL database f...

Snowflake Scripting - SQL Cursors

Snowflake scripting in SQL seems to be in preview and I have decided to have a play with it. Given how new it is there is limited documentation so I am using a combination of what I can find on the Snowflake site and the odd blog that has been written about it. There appear to be a few quirks, at least when compared to Oracle PL/SQL (though that has been round for years). How many of these are intentional and how many are things to be ironed out I don't know. You can see the procedure I have created it:  Accepts an id as a parameter  Creates a result set selecting from a table, using the parameter as a filter Loads the results set into a cursor.  Loops through the cursor loading the id in the cursor into variable Calls procedure passing in the variable as the parameter.  Then as a proof of concept I tried the Snowflake feature of allowing declaration of variables within the main start and end block.