Hi Guys, we are currently relying on Prefect 1.2 f...
# prefect-community
o
Hi Guys, we are currently relying on Prefect 1.2 for some critical production ETLs. We are starting to discuss whether we should consider moving to Prefect 2.0. However, I can't find anything in the documentation related to an Imperative API, Do we still have one in Prefect 2.0?
k
There is done, and it’s also not really recommended for Prefect 1 because it’s harder to use for end users
o
Thanks Kevin for the clarification (I'm assuming you meant there is none 😄 ) , I agree that its harder to use with End Users, but it was a bit easier when using it to integrate prefect with some of our work. I will start investigating how we can refactor our code to use functional API Thanks again and good luck with your next move 🙂
k
Yes none
and thank you!
👍 1
o
Hey @Kevin Kho just had a follow up question as I'm still exploring the migration to 2.0 and trying to figure out how our code will work if we do decide to migrate. Can we: • Can we use the Task class to create tasks and define their run function or do I have to use the @task decorater when defining tasks? • Can we subclass the Task class? So we can add some extra attributes and functionality to a task that can then be used as the main class for any Task?