Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Status of testing Providers that were prepared on February 08, 2023 #29424

Closed
20 of 58 tasks
eladkal opened this issue Feb 8, 2023 · 8 comments
Closed
20 of 58 tasks

Status of testing Providers that were prepared on February 08, 2023 #29424

eladkal opened this issue Feb 8, 2023 · 8 comments
Labels
kind:meta High-level information important to the community testing status Status of testing releases

Comments

@eladkal
Copy link
Contributor

eladkal commented Feb 8, 2023

Body

I have a kind request for all the contributors to the latest provider packages release.
Could you please help us to test the RC versions of the providers?

Let us know in the comment, whether the issue is addressed.

Those are providers that require testing as there were some substantial changes introduced:

Provider amazon: 7.2.0rc1

Provider apache.beam: 4.2.0rc1

Provider apache.hive: 5.1.2rc1

Provider arangodb: 2.1.1rc1

Provider cncf.kubernetes: 5.2.0rc1

Provider dbt.cloud: 3.0.0rc1

Provider elasticsearch: 4.4.0rc1

Provider ftp: 3.3.1rc1

Provider google: 8.9.0rc1

Provider microsoft.azure: 5.2.0rc1

Provider mysql: 4.0.1rc1

Provider presto: 4.2.2rc1

Provider sftp: 4.2.2rc1

Provider snowflake: 4.0.3rc1

Provider tableau: 4.1.0rc1

Provider trino: 4.3.2rc1

The guidelines on how to test providers can be found in

Verify providers by contributors

Contributors are also encouraged to cast vote in the mailing list thread.

All users involved in the PRs:
@BasPH @VladaZakharova @bkossakowska @pankajkoti @phanikumv @MaksYermak @RachitSharma2001 @vandonr-amz @IAL32 @raphaelauv @Taragolis @dwreeves @potiuk @snjypl @dstandish @vchiapaikeo @eladkal @shahar1
@jedcunningham @csm10495 @josh-fell @joarobles @johannaojeling @o-nikolas @wonhyeongseo @seunggabi @MrGeorgeOwl @hussein-awala @maggesssss

Committer

  • I acknowledge that I am a maintainer/committer of the Apache Airflow project.
@eladkal eladkal added kind:meta High-level information important to the community testing status Status of testing releases labels Feb 8, 2023
@pankajkoti
Copy link
Member

pankajkoti commented Feb 9, 2023

Thanks @eladkal . I tested my PR #29349 which is part of Provider google: 8.9.0rc1 and it works fine.

@seunggabi
Copy link
Contributor

Thanks @eladkal .
I tested a minute ago.

#29360: @seunggabi
https://pypi.org/project/apache-airflow-providers-tableau/4.1.0rc1/

It was works.

from airflow.providers.tableau.operators.tableau import TableauOperator

...

task_refresh_workbook_blocking = TableauOperator(
    resource="workbooks",
    method="refresh",
    match_with="{{ params.match_with }}",
    find="{{ params.find }}",
    blocking_refresh=True,
    task_id="refresh_tableau_workbook_blocking",
    dag=dag,
)

스크린샷 2023-02-10 오전 12 11 31

@johannaojeling
Copy link
Contributor

#28764 is tested with the Beam RC and works as expected

@csm10495
Copy link
Contributor

csm10495 commented Feb 9, 2023

#28808 still seems legit

@vchiapaikeo
Copy link
Contributor

#28959 looks good

write_on_empty=False (default)
image

write_on_empty=True
image

@o-nikolas
Copy link
Contributor

o-nikolas commented Feb 9, 2023

I added code to kill the process while running to test the emr on_kill changes, and the cleanup code ran successfully (and I confirmed the resource was deleted in my AWS account):

INFO  [airflow.task.operators] Job flow with id j-1ADYKTIV4THO5 created
INFO  [airflow.task.operators] SLEEPING NOW, KILL THE PROCESS TO TEST ON_KILL
INFO  [airflow.task.operators] TRYING TO KILL MYSELF
ERROR [airflow.task] Received SIGTERM. Terminating subprocesses.
INFO  [airflow.task.operators] Terminating job flow j-1ADYKTIV4THO5

While I was there, I tested the wait_for_completion changes on the same operator. It worked successfully:

INFO  [airflow.task] Executing <Task(EmrCreateJobFlowOperator): create_job_flow> on 2021-01-01 00:00:00+00:00
INFO  [airflow.task] Exporting env vars: AIRFLOW_CTX_DAG_OWNER='airflow' AIRFLOW_CTX_DAG_ID='example_emr' AIRFLOW_CTX_TASK_ID='create_job_flow' AIRFLOW_CTX_EXECUTION_DATE='2021-01-01T00:00:00+00:00' AIRFLOW_CTX_TRY_NUMBER='1' AIRFLOW_CTX_DAG_RUN_ID='backfill__2021-01-01T00:00:00+00:00'
INFO  [airflow.task.operators] Creating job flow using aws_conn_id: aws_default, emr_conn_id: emr_default
INFO  [airflow.hooks.base] Using connection ID 'emr_default' for task execution.
INFO  [airflow.hooks.base] Using connection ID 'aws_default' for task execution.
INFO  [botocore.credentials] Found credentials in environment variables.
INFO  [airflow.task.operators] Job flow with id j-2VDGDHAR3ASCT created
INFO  [airflow.providers.amazon.aws.utils.waiter] Waiting for job flow to be finished.
INFO  [airflow.providers.amazon.aws.utils.waiter] Waiting for job flow to be finished.
INFO  [airflow.providers.amazon.aws.utils.waiter] Waiting for job flow to be finished.
INFO  [airflow.providers.amazon.aws.utils.waiter] Waiting for job flow to be finished.
INFO  [airflow.providers.amazon.aws.utils.waiter] Waiting for job flow to be finished.

I marked both changes as tested above in the task list.

@josh-fell
Copy link
Contributor

Thanks for organizing @eladkal!

All of the dbt Cloud changes look good as well as the Python API docs change in #29041.

@eladkal
Copy link
Contributor Author

eladkal commented Feb 11, 2023

Thank you everyone.
Providers are released
I invite everyone to help improve providers for the next release, a list of open issues can be found here.

@eladkal eladkal closed this as completed Feb 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind:meta High-level information important to the community testing status Status of testing releases
Projects
None yet
Development

No branches or pull requests

8 participants