Add DAG and table maintenance for wmf_content.mediawiki_content_current_v1 (!1249) · Merge requests · repos / data-engineering / Airflow DAGs · GitLab

How to register an account on GitLab. Due to spam, new accounts are locked until approved by an admin or the approver bot. Your GitLab account gets automatically approved within one hour if you are a member of Trusted Contributors in Gerrit, or a member of the Trusted-Contributors group in Phabricator and linked your Developer account ("LDAP") to your Phabricator account. If none of these apply, file an unlock request to expedite access. Only if you are WMF staff: Create your GitLab account, have "Wmf" group membership in IDM, link your Developer account ("LDAP") to your Phabricator account, and get automatically approved.

Support: mw:GitLab, how to host a project on GitLab, #wikimedia-gitlab on libera.chat, #GitLab on Phabricator.

Take the 2025 Developer Satisfaction Survey ^{(privacy statement)} to help identify areas for improvement and measure satisfaction within the Wikimedia developer community.

(Depends on repos/data-engineering/dumps/mediawiki-content-dump!62).

In this MR we:

Implement a daily DAG to calculage and merge changes from wmf_content.mediawiki_content_history_v1 into wmf_content.mediawiki_content_current_v1. This is done via a MERGE INTO, which is under review separately.
Implement Iceberg table maintenance for wmf_content.mediawiki_content_current_v1, including a call to rewrite_position_delete_files() which allows us to run the MERGE INTO pipeline with merge-on-read (faster, and more stable!).
Modified folder hierarchy a bit to accomodate the set of history content jobs vs the current jobs.

Edited Apr 17, 2025 by Xcollazo