Add query nft trades labels

[soispoke]

Brief comments on the purpose of your changes:
This PR aims to give an example of adding query labels to the spellbook repo

For Dune Engine V2
I've checked that:
General checks:

• I tested the query on dune.com after compiling the model with dbt compile (compiled queries are written to the target directory)
• I used "refs" to reference other models in this repo and "sources" to reference raw or decoded tables
• if adding a new model, I added a test
• the filename is unique and ends with .sql
• each sql file is a select statement and has only one view, table or function defined
• column names are lowercase_snake_cased
• if adding a new model, I edited the dbt project YAML file with new directory path for both models and seeds (if applicable)
• if adding a new model, I edited the alter table macro to display new database object (table or view) in UI explorer
• if adding a new materialized table, I edited the optimize table macro

Join logic:

• if joining to base table (i.e. ethereum transactions or traces), I looked to make it an inner join if possible

Incremental logic:

• I used is_incremental & not is_incremental jinja block filters on both base tables and decoded tables
  • where block_time >= date_trunc("day", now() - interval '1 week')
• if joining to base table (i.e. ethereum transactions or traces), I applied join condition where block_time >= date_trunc("day", now() - interval '1 week')
• if joining to prices view, I applied join condition where minute >= date_trunc("day", now() - interval '1 week')

[aalan3]

We need to also add an alter table statement for this. Could you try adding it to post_hook here, would be interesting to see if it works. Because then we can keep those things in the files and not forget.

[soispoke]

Yes, I initially didn't want to expose the labels yet, until we have added a couple more queries/static labels. I also don't really want to add alter table statements as post hook as I've done this before and it ended up being extremely long and messy in the dbt_project.yml file. I think the most promising avenue is to alter table properties in the models directly (databricks/dbt-databricks#33), but we have to wait until the databricks adapter is supported by dbt cloud.

In any case, maybe we could open another PR/discussion around this ?

[aalan3]

not that important but these are all in the future

[soispoke]

oh right thanks haha, this is fixed now 👍

[aalan3]

drop ?, here and below

[soispoke]

sounds good, done @aalan3

[jeff-dude]

this builds fine, but a bit slow to query the end result in 'all' table, at least when trying to do select * on it. not a huge surprise as it's on large volume of nft trades data.

also curious how you proceed with the few PRs all for labels? merge one PR, then merge main into other branch(s) and increment from there, considering they all need to union into the 'all' table?

[soispoke]

@jeff-dude thanks, yes exactly the goal was to give examples for static labels and query labels for it to be easier to review, but now I'll merge this, and then merge main into the bigger Labels WIP PR #1474. If you guys can review/approve that one when you have time it would be awesome