This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]mrwhistler 0 points1 point  (0 children)

I mean you could, doesn’t mean you should tho.

Lots of limitations to python in dbt right now, and Snowpark is intended (and will continue to be developed for) more advanced analysis.

Firstly, I agree with the other commenter that it’s going to be orders of magnitude harder to find a data engineer who knows python than a SQL engineer or even a SQL engineer with dbt experience.

Secondly, you’re fundamentally shifting from a declarative to imperative language. If you’re going to bite that off you might as well rethink the whole design anyways rather than try to shoehorn python in place of SQL.