Skip to content

Conversation

bhirsz
Copy link
Contributor

@bhirsz bhirsz commented Apr 6, 2022

Migrate GCS system tests/example dags to be compliant with new design (AIP-47).

Covers
airflow/providers/google/cloud/example_dags/example_gcs.py
airflow/providers/google/cloud/example_dags/example_gcs_timespan_file_transform.py
airflow/providers/google/cloud/example_dags/example_gcs_to_gcs.py
airflow/providers/google/cloud/example_dags/example_gcs_to_local.py
airflow/providers/google/cloud/example_dags/example_local_to_gcs.py
from #22447

@bhirsz bhirsz requested review from mik-laj and turbaszek as code owners April 6, 2022 11:37
@boring-cyborg boring-cyborg bot added area:providers kind:documentation provider:google Google (including GCP) related issues labels Apr 6, 2022
@bhirsz
Copy link
Contributor Author

bhirsz commented Apr 6, 2022

The PR is bigger than I want but it's mostly because there are several setup fixtures in old design (in pytest classes) that can now be covered by operators - thus the structure changed and multiple examples had to be done in one go. Everything relates to gcs though.

@Bowrna
Copy link
Contributor

Bowrna commented Apr 10, 2022

@bhirsz
I tried to write a similar system tests design for Elasticsearch and I was running into issues. (#22811)
Can you help me by telling me if you faced similar issues like the one in the comments in this PR?
It would be helpful if you could check this PR and point out mistakes if there is any in it.

@bhirsz
Copy link
Contributor Author

bhirsz commented Apr 11, 2022

I tried to write a similar system tests design for Elasticsearch and I was running into issues. (#22811)
Can you help me by telling me if you faced similar issues like the one in the comments in #22811 (comment) PR?
It would be helpful if you could check this PR and point out mistakes if there is any in it.

I've commented in your PR. But I've also encountered this problem whenever I run the same DAG_ID twice in the same environment (resetting env or using unique name between runs helps). I will investigate why it happens.

Bartlomiej Hirsz added 2 commits April 12, 2022 06:10
Change-Id: I2aeb518d236296bcdbd489850ed1813cefc0ce3f
Change-Id: I2558eab8a98706e693c0cc9bed8bc33354e6a23f
Bartlomiej Hirsz added 2 commits April 12, 2022 08:53
Change-Id: I4d7d88e13de00b25cbce66b0319870cae1be249b
Change-Id: Iec9be2369a93f2b9bab62f6e5eef298492852c90
@bhirsz bhirsz force-pushed the gcs_system_tests branch from 7665283 to 5bb09f6 Compare April 12, 2022 09:01
@bhirsz
Copy link
Contributor Author

bhirsz commented Apr 13, 2022

I tried to write a similar system tests design for Elasticsearch and I was running into issues. (#22811)
Can you help me by telling me if you faced similar issues like the one in the comments in #22811 (comment) PR?
It would be helpful if you could check this PR and point out mistakes if there is any in it.

I've commented in your PR. But I've also encountered this problem whenever I run the same DAG_ID twice in the same environment (resetting env or using unique name between runs helps). I will investigate why it happens.

Resolved by changing State.NONE (which works only for Tasks) to State.Queued (default state for dag)

bhirsz and others added 7 commits April 13, 2022 07:41
Change-Id: I8af21344a836c232ff505c1442b960253eec31b7
…into gcs_system_tests

Change-Id: Ie7a572289872d10c649d8697a5819ddcac9d9e99
Change-Id: I2aeb518d236296bcdbd489850ed1813cefc0ce3f
Change-Id: I2558eab8a98706e693c0cc9bed8bc33354e6a23f
Change-Id: Iec9be2369a93f2b9bab62f6e5eef298492852c90
Change-Id: I8af21344a836c232ff505c1442b960253eec31b7
@potiuk potiuk force-pushed the gcs_system_tests branch from 6492a1e to 6e8baa6 Compare