hey all - trying to use the snowflake resource and I can't make heads or tails of what patterns are supported. I expected to be able to run

foo1

from here, but it failed, then i expected to run

foo2

like here but it failed. Then i tried

foo3

from here, and that worked for me. The pattern I'd prefer to encourage others to use is the first -- is that supported?

from dagster import Definitions, asset, OpExecutionContext
from dagster_snowflake import SnowflakeResource

@asset
def foo(context: OpExecutionContext, snowflake: SnowflakeResource):
    result = snowflake.execute_query("select 1")
    <http://context.log.info|context.log.info>(result)

@asset
def foo2(context: OpExecutionContext, snowflake: SnowflakeResource):
    with snowflake.get_connection() as conn:
        result = conn.execute_query("select 1")
    <http://context.log.info|context.log.info>(result)

@asset
def foo3(context: OpExecutionContext, snowflake: SnowflakeResource):
    with snowflake.get_connection() as conn:
        result = conn.cursor().execute("select 1")
    <http://context.log.info|context.log.info>(result)

defs = Definitions(
    assets=[foo, foo2, foo3],
    resources={
        "snowflake": SnowflakeResource(
            account="whatnot-prod",
            user=SNOWFLAKE_USER,
            password=SNOWFLAKE_PASSWORD,
            role="STAGE_ADMIN_ROLE",
            warehouse="STAGE_LOAD_WH",
            database="STAGE",
        )
    }
)

ack SnowflakeResource should definitely be in the docs. That’s an oversight/bug as i’m pretty sure it was there at one point. apologies for that. So the difference in API here is because in the old style snowflake resource

snowflake_resource

we wrote our own SnowflakeConnection class with those helper functions. For the new pythonic snowflake resource

SnowflakeResource

we instead chose to just directly wrap snowflakes

SnowflakeConnector

class (an annoying and unfortunate naming collision)

I can understand that perspective, but I think at least offering

execute_query

and

execute_queries

for parity (even without the

fetch_pandas_result

, would be nice. Otherwise there's almost no benefit to using a resource class except for config management. But, if that's the approach that's going to be taken with other adapters (basically no additional functionality on resources), then it makes sense.

yeah i’ll bring it up with some other folks and we can chat about it