potiuk commented on pull request #22305: URL: https://github.com/apache/airflow/pull/22305#issuecomment-1084282464
I think `dags` command is conceptualy different than `celery` as `celery` is really there to manage "celery workers". Dag is there mostly to manage "dags" and do some actions around it. Somehow `dags parser` or `dags processor` does not feel like belonging to the same group as `dags list` or `dags test`. Those are kind of dfferent "lifecycle". I think the main reason "worker" is under "celery" is that the whole "celery" group is disabled when celery executor is not used. I'd say "dags processor/parser" is a "core" component - similar as scheduler, webserver, triggerer - especially when we go into more isolation mode, it deserves "top-level" entry. I also thing "dags-parser" is worse than "dags-processor". One - because it introduces a new name, we already have DagProcessor and what it does is conceptually the same as the separated command. And Two - DagsProcessor does more than parsing - it Parses, Serializes, Stores the DAGS in the database but also executes Dag Callbacks. So by all mean "dags-parser" does not do the justice to what tthis component does. The `dags-processor` is much more accurate. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
