implementation guideline

[dataders]

Resolves #
Depends on: #471

Description

mostly worked on the python class tuff

• applied state
• relation-specific drop and rename
• modify materializations according to above
• (not all the way done yet) Python class configs
• new MV tests

Checklist

• I have run this code in development and it appears to resolve the stated issue
• This PR includes tests, or tests are not required/relevant for this PR
• I have updated the CHANGELOG.md and added information about my change to the "dbt-databricks next" section.

[benc-db]

Please see tests failing re: hologram removal.

[benc-db]

@dataders is this ready for me to take over or do you still plan on another commit?

[dataders]

@dataders is this ready for me to take over or do you still plan on another commit?

not even close. 🥲 i'll be working on this more today and tomorrow. stay tuned.

also dbt-spark 1.6.0b2 (which includes the hologram work dbt-labs/dbt-spark#880) is being cut as we speak. this'll obviate my most recent commit

[dataders]

@mikealfare how can I change this to use list_relations_without_caching() instead? in my mind that's where this logic is already standardized.

in the case of dbt-databricks, it all the logic is in Python ( DatabricksAdapter.get_relations_without_caching(). I'd rather not duplicate/reimplement it

[dataders]

in the meantime, i suppose this is a decent woraround

    select
        'table' as relation_type
    from information_schema.tables
    where schemaname = '{relation.schema}'
    and tablename = '{relation.identifier}'
    union all
    select
        case when
            is_materialized = TRUE then 'materialized_view'
            else 'view'
        end as relation_type
    from information_schema.views
    where schemaname = '{relation.schema}'
    and viewname = '{relation.identifier}'

[benc-db]

So long as its only used with the UC cluster...information schema isn't available on the non-uc cluster.

[benc-db]

@dataders status update? At any point feel free to hand off and give me instructions on what is remaining :).

[dataders]

@dataders status update? At any point feel free to hand off and give me instructions on what is remaining :).
@benc-db ask and you shall receive :) #473

[benc-db]

@dataders status update? At any point feel free to hand off and give me instructions on what is remaining :).

you @benc-db ask and you shall receive :) #473

Ok, taking it now.

[dataders]

@benc-db, after discussing internally, we're dropping this MV refactor work as a requirement for 1.7.0rc1 or even 1.7.0, but since you already have your hands on it, I wanted to show the next step. I was afraid to push directly to the branch in this PR, so I made dataders#1 that you can pull in if you like. #477 gives more context