Go to file
2023-01-13 13:22:33 -08:00
.github/workflows hourly test to check bronze partitions are loaded properly into silver (#208) 2023-01-12 11:51:05 -08:00
analysis dbt proj files and sp setup 2022-02-25 14:49:40 -08:00
data add workflow for get_token_data macro (#190) 2022-12-16 15:18:51 -08:00
docs update docs 2022-11-03 08:39:25 -07:00
macros custom query tags (#184) 2022-12-13 17:09:50 -08:00
models this model gets full refreshed daily, should test items <= prev day (#212) 2023-01-13 11:24:41 -08:00
snapshots dbt proj files and sp setup 2022-02-25 14:49:40 -08:00
tests hourly test to check bronze partitions are loaded properly into silver (#208) 2023-01-12 11:51:05 -08:00
.env.sample An 2510/GitHub dbt workflows (#167) 2022-11-30 15:50:35 -08:00
.gitignore Hotfix/reingest full parts to fix partial load (#205) 2023-01-11 09:20:34 -08:00
dbt_project.yml An 2510/solana incrementals (#183) 2022-12-08 15:25:36 -08:00
docker-compose.yml add community curation resources (#138) 2022-10-18 13:09:55 -07:00
Dockerfile add community curation resources (#138) 2022-10-18 13:09:55 -07:00
LICENSE Initial commit 2022-02-25 14:28:59 -08:00
Makefile add community curation resources (#138) 2022-10-18 13:09:55 -07:00
packages.yml allow solana to run on dbt 1.2 (#197) 2023-01-02 18:25:30 -08:00
profiles.yml An 2510/solana incrementals (#183) 2022-12-08 15:25:36 -08:00
README.md update tags readme 2023-01-13 13:22:33 -08:00

Profile Set Up

Use the following within profiles.yml


solana:
  target: dev
  outputs:
    dev:
      type: snowflake
      account: <ACCOUNT>
      role: <ROLE>
      user: <USERNAME>
      password: <PASSWORD>
      region: <REGION>
      database: SOLANA_DEV
      warehouse: <WAREHOUSE>
      schema: SILVER
      threads: 4
      client_session_keep_alive: False
      query_tag: <TAG>

Notes

  • block_id column in our data models matches what Solcan classifies as Block. This value is same as what is referred to as Slot.

Resources:

  • Learn more about dbt in the docs
  • Check out Discourse for commonly asked questions and answers
  • Join the chat on Slack for live discussions and support
  • Find dbt events near you
  • Check out the blog for the latest news on dbt's development and best practices

Applying Model Tags

Database / Schema level tags

Database and schema tags are applied via the add_database_or_schema_tags macro. These tags are inherited by their downstream objects. To add/modify tags call the appropriate tag set function within the macro.

{{ set_database_tag_value('SOME_DATABASE_TAG_KEY','SOME_DATABASE_TAG_VALUE') }}
{{ set_schema_tag_value('SOME_SCHEMA_TAG_KEY','SOME_SCHEMA_TAG_VALUE') }}

Model tags

To add/update a model's snowflake tags, add/modify the meta model property under config. Only table level tags are supported at this time via DBT.

{{ config(
    ...,
    meta={
        'database_tags':{
            'table': {
                'PURPOSE': 'SOME_PURPOSE'
            }
        }
    },
    ...
) }}

By default, model tags are not pushed to snowflake on each load. You can push a tag update for a model by specifying the UPDATE_SNOWFLAKE_TAGS project variable during a run. All views MUST be run with this setting otherwise the existing tags will be erased because DBT is re-creating the view each time it runs.

dbt run --var '{"UPDATE_SNOWFLAKE_TAGS":True}' -s models/core/core__fact_swaps.sql

Querying for existing tags on a model in snowflake

select *
from table(solana.information_schema.tag_references('solana.core.fact_blocks', 'table'));