Chenyu Li

@josephberni I think we might need @daniel-murray to sign the CLA to get this merged

This is because when we implement the lambda function, we made it only allow 1 argument instead of arbitrary at https://github.com/dbt-labs/dbt-core/blob/4d6208be6464a48a078dd8000ae6c29d8d7a42ce/core/dbt/include/global_project/macros/python_model/python.sql#L72-L77 The fix should just modify the lambda function to...

Hey @barberscott, thanks for opening this, and I can see the frustration of the unintended behavior it causes. Looks like this is the place where we set the default value...

Changed upper limit to include @jtcohen6 's recent change for requirements

I will leave this to the adapter team to take a second pass and merge(assuming all tests passes, I don't see any reason they won't)

@ilanbenb sorry for the delay! I am merging this for the the Adapter team as all feedback has been addressed. Thanks for the contribution!

Updates that came from some pairing time with @stu-k today: If we write our materialization macro as something like: ```jinja {% materialization seed, adapter='snowflake', language=['sql'] %} actual logic {% endmaterialization...

We should consider deprecating the jinja `print` in favor of using `log` when working on this ticket.

@graciegoheen As of the change we added [here](https://github.com/dbt-labs/dbt-core/pull/9328/files#diff-af95c60156433e0ad9e3bf2754821f4511e6a9579f6414928fab7b0027f97b05R68), you can specify just `--state` path and it should find the `result.json` in the state dir and use that.

@dbeatty10 why only bigquery and snowflake?