Revamp NFT to new sector spell design structure

[0xRobin]

Adapt the NFT sector top level models after the discussion in #4637

The structure:

• platform models (blur_ethereum_base_trades.sql) - base schema, materialized
• chain union (nft_ethereum_base_trades.sql) - base schema, view
• full union (nft_base_trades.sql) - base schema, materialized
• enrichment (nft_trades_beta.sql) - full schema, view

specific to NFT, a final layer on top to keep compatibility to the currently exposed column names:

• backwards port (nft_trades.sql) - full schema (old), view, exposed on Dune

[0xRobin]

Hmm. can't figure our where this error is coming from..

[jeff-dude]

okay, last piece of feedback i think 🤞

check out the warnings in the dbt compile step of CI. i've noticed this a few times on recent merges, where we forget to check there and then the warnings pop up in prod / user's local setups once syncing with main branch. can you look to clean those warnings up here?

[jeff-dude]

i merged in #4848 since we've had warnings pop through often post version upgrade. now you can see CI fail on that step.

[0xRobin]

it's weird that I don't get this compile warning locally.. 🤔

[jeff-dude]

it's weird that I don't get this compile warning locally.. 🤔

yeah, i've noticed that too sometimes. usually the warnings i see in CI end up being true gaps though. let me know if that isn't the case here and something else odd is going on

[0xRobin]

I was able to get them locally now, might be a partial of full parse thing.
Downside, the current CI setup is "fail-fast" meaning you only get to see the first warning..
There doesn't seem to be an option to make it error but not exit on warnings though.

[jeff-dude]

I was able to get them locally now, might be a partial of full parse thing. Downside, the current CI setup is "fail-fast" meaning you only get to see the first warning.. There doesn't seem to be an option to make it error but not exit on warnings though.

yep, i had to do:
dbt clean
dbt deps
dbt compile

i should probably alias that locally to run all three every time i do dbt compile

Downside, the current CI setup is "fail-fast" meaning you only get to see the first warning..
There doesn't seem to be an option to make it error but not exit on warnings though.

agree on this, but at the same time, this should be relatively rare. your PR is unique in terms of moving / restructuring, ideally that is less often and/or us internally doing the heavy lifting on that.