Size: a a a

PiterPy Conf Сhat

2020 August 04

KN

Kaxil Naik in PiterPy Conf Сhat
The graph itself is just rendered after de-serializing the Serialized_dag
источник

KN

Kaxil Naik in PiterPy Conf Сhat
Yuliya Volkova
yea) I mean that process add to DB info about new DAG at the first time?
Oh yeah, the scheduler continually parses new DAG files and stores the new DAGs in both "dag" table and in serialized_dag table
источник

YV

Yuliya Volkova in PiterPy Conf Сhat
Kaxil Naik
Oh yeah, the scheduler continually parses new DAG files and stores the new DAGs in both "dag" table and in serialized_dag table
got it, it done by scheduler, not by webserver
источник

KN

Kaxil Naik in PiterPy Conf Сhat
Yeah -- this was done so that Webserver becomes light-weight
источник

KN

Kaxil Naik in PiterPy Conf Сhat
And parsing of DAGs only happens at one place -- "Scheduler"
источник

KN

Kaxil Naik in PiterPy Conf Сhat
Webserver just reads everything from the DB
источник

YV

Yuliya Volkova in PiterPy Conf Сhat
Kaxil Naik
And parsing of DAGs only happens at one place -- "Scheduler"
cool, make sense
источник

KN

Kaxil Naik in PiterPy Conf Сhat
it no longer needs access to DAG files
источник

KN

Kaxil Naik in PiterPy Conf Сhat
источник

KN

Kaxil Naik in PiterPy Conf Сhat
источник

YV

Yuliya Volkova in PiterPy Conf Сhat
very cool and informative talk ) thank you
источник

KN

Kaxil Naik in PiterPy Conf Сhat
Thanks Iuliia :)
источник

IS

Irina Saribekova in PiterPy Conf Сhat
Время вопросов :)
источник

YV

Yuliya Volkova in PiterPy Conf Сhat
@kaxil one more question from me) what about ML, do you think that Airflow will cover 'ML-fields' in feature or better to focus on things like ML Flow https://mlflow.org/  if need to care about ML tasks?
источник

YV

Yuliya Volkova in PiterPy Conf Сhat
I remember was some mails about it in dev airflow maillist, but not sure that was a result of discussion
источник

KN

Kaxil Naik in PiterPy Conf Сhat
Thats a great question. One of the main motivation of the Functional DAGs was to support ML use-cases where the Data Scientist don't need to worry about Airflow syntaxes instead they can just write the same Python Code.

Twitter uses it interally for their ML Workflows. Here is a blog post on how they do it: https://blog.twitter.com/engineering/en_us/topics/insights/2018/ml-workflows.html
источник

KN

Kaxil Naik in PiterPy Conf Сhat
And also we want to support more ML use-cases with Airflow so we are planning to have a native View to see how the models performed in the previous runs via some user-configurable metric like rmse value. However if they would also want to scheduler other pipelines ETL or anything else, Airflow would be ideal
источник

KN

Kaxil Naik in PiterPy Conf Сhat
I would say though that MLFlow specializes in ML Worflows so if a company only wants to have ML pipeline, they would be better with MLFlow instead of Airflow
источник

IS

Irina Saribekova in PiterPy Conf Сhat
Сейчас в эфире @switowski
С темой: Wait, IPython can do that?!

Во время доклада отмечайте спикера и задавайте вопросы в чате на английском, он вам ответит.

Вопросы на русском также можно писать, их модератор задаст в прямом эфире после доклада.

Если хотите задать вопрос лично в эфире, проверяйте свою камеру и гарнитуру и пишите мне в личку :)
источник

YV

Yuliya Volkova in PiterPy Conf Сhat
Kaxil Naik
I would say though that MLFlow specializes in ML Worflows so if a company only wants to have ML pipeline, they would be better with MLFlow instead of Airflow
got it) thank you for the answers
источник