Reviewed by Aditya Kumar Β· Last reviewed 2026-03-24
Oozie uses workflow.xml (DAG), coordinator.xml (scheduling), bundle.xml (multi-coordinator). One workflow.xml per workflow; 1β10+ per org depending on pipeline complexity. WHY: Oozie is XML-based, Hadoop-native; Airflow has largely replaced it for Python DAGs and ecosystem....
Oozie uses workflow.xml (DAG), coordinator.xml (scheduling), bundle.xml (multi-coordinator). One workflow.xml per workflow; 1β10+ per org depending on pipeline complexity. WHY: Oozie is XML-based, Hadoop-native; Airflow has largely replaced it for Python DAGs and ecosystem. SCALABILITY: Modular workflows and parameterization scale; version control in Git. COST: Oozie runs on Hadoop; Airflow is lighter and cloud-native.
Red Flag: Not knowing the file structure. Pro-Move: 'We migrated 15 Oozie workflows to Airflow; reduced config by 60% with Python DAGs; kept coordinator patterns for backfill.'
According to DataEngPrep.tech, this is one of the most frequently asked General/Other interview questions, reported at 1 company. DataEngPrep.tech maintains an editor-reviewed database of 1,863 data engineering interview questions across 7 categories.