Merge Delete from BQ and Insert from GCS to BQ into a Single Atomic Operation for achieving Idempotency

README.md

@@ -548,6 +548,7 @@ This section contains information about the Airflow setup. It includes our DAG d
   - [build_delete_data_task](#build_delete_data_task)
   - [build_dbt_task](#build_dbt_task)
   - [build_elementary_slack_alert_task](#build_elementary_slack_alert_task)
+  - [build_del_ins_from_gcs_to_bq_task](#build_del_ins_from_gcs_to_bq_task)
 
 ---
 
@@ -668,6 +669,10 @@ This section contains information about the Airflow setup. It includes our DAG d
 
 [This file](https://github.com/stellar/stellar-etl-airflow/blob/master/dags/stellar_etl_airflow/build_gcs_to_bq_task.py) contains methods for creating tasks that appends information from a Google Cloud Storage file to a BigQuery table. These tasks will create a new table if one does not exist. These tasks are used for history archive data structures, as Stellar wants to keep a complete record of the ledger's entire history.
 
+### **build_del_ins_from_gcs_to_bq_task**
+
+[This file](https://github.com/stellar/stellar-etl-airflow/blob/master/dags/stellar_etl_airflow/build_del_ins_from_gcs_to_bq_task.py) contains methods for deleting data from old partitions if the table exists and also import fresh data from gcs to the corresponding Big Query table. These tasks will create a new table if one does not exist. These tasks are used for history archive data structures, as Stellar wants to keep a complete record of the ledger's entire history.
+
 ### **build_apply_gcs_changes_to_bq_task**
 
 [This file](https://github.com/stellar/stellar-etl-airflow/blob/master/dags/stellar_etl_airflow/build_apply_gcs_changes_to_bq_task.py) contains methods for creating apply tasks. Apply tasks are used to merge a file from Google Cloud Storage into a BigQuery table. Apply tasks differ from the other task that appends in that they apply changes. This means that they update, delete, and insert rows. These tasks are used for accounts, offers, and trustlines, as the BigQuery table represents the point in time state of these data structures. This means that, for example, a merge task could alter the account balance field in the table if a user performed a transaction, delete a row in the table if a user deleted their account, or add a new row if a new account was created.

airflow_variables_dev.json

@@ -334,6 +334,7 @@
     "asset_stats": 720,
     "build_batch_stats": 840,
     "build_bq_insert_job": 1080,
+    "build_del_ins_from_gcs_to_bq_task": 2000,
     "build_delete_data_task": 1020,
     "build_export_task": 840,
     "build_gcs_to_bq_task": 960,
@@ -367,6 +368,7 @@
     "build_bq_insert_job": 180,
     "build_copy_table": 180,
     "build_dbt_task": 960,
+    "build_del_ins_from_gcs_to_bq_task": 400,
     "build_delete_data_task": 180,
     "build_export_task": 420,
     "build_gcs_to_bq_task": 300,

airflow_variables_prod.json

@@ -332,6 +332,7 @@
     "asset_stats": 420,
     "build_batch_stats": 600,
     "build_bq_insert_job": 840,
+    "build_del_ins_from_gcs_to_bq_task": 2000,
     "build_delete_data_task": 780,
     "build_export_task": 600,
     "build_gcs_to_bq_task": 660,
@@ -365,6 +366,7 @@
     "build_bq_insert_job": 180,
     "build_copy_table": 180,
     "build_dbt_task": 1800,
+    "build_del_ins_from_gcs_to_bq_task": 400,
     "build_delete_data_task": 180,
     "build_export_task": 300,
     "build_gcs_to_bq_task": 300,