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 September 08, 2023 #34218

Closed
eladkal opened this issue Sep 8, 2023 · 20 comments
Closed

Status of testing Providers that were prepared on September 08, 2023 #34218

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

Comments

@eladkal
Copy link
Contributor

eladkal commented Sep 8, 2023

Body

Issue title: Status of testing Providers that were prepared on September 08, 2023

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?

The guidelines on how to test providers can be found in

Verify providers by contributors

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 airbyte: 3.3.2rc1

Provider alibaba: 2.5.3rc1

Provider amazon: 8.7.0rc1

Provider apache.beam: 5.2.3rc1

Provider apache.drill: 2.4.4rc1

Provider apache.flink: 1.1.3rc1

Provider apache.hdfs: 4.1.1rc1

Provider apache.hive: 6.1.6rc1

Provider apache.impala: 1.1.3rc1

Provider apache.livy: 3.5.4rc1

Provider apache.pig: 4.1.2rc1

Provider apache.pinot: 4.1.4rc1

Provider apprise: 1.0.2rc1

Provider celery: 3.3.4rc1

Provider cncf.kubernetes: 7.5.1rc1

Provider common.sql: 1.7.2rc1

Provider databricks: 4.5.0rc1

Provider dbt.cloud: 3.3.0rc1

Provider docker: 3.7.5rc1

Provider elasticsearch: 5.0.2rc1

Provider exasol: 4.2.5rc1

Provider facebook: 3.2.2rc1

Provider ftp: 3.5.2rc1

Provider google: 10.8.0rc1

Provider hashicorp: 3.4.3rc1

Provider http: 4.5.2rc1

Provider imap: 3.3.2rc1

Provider influxdb: 2.2.3rc1

Provider jdbc: 4.0.2rc1

Provider jenkins: 3.3.2rc1

Provider microsoft.azure: 7.0.0rc1

Provider microsoft.psrp: 2.3.2rc1

Provider mongo: 3.2.2rc1

Provider mysql: 5.3.1rc1

Provider neo4j: 3.3.3rc1

Provider openlineage: 1.1.0rc1

Provider oracle: 3.7.4rc1

Provider pagerduty: 3.3.1rc1

Provider postgres: 5.6.1rc1

Provider presto: 5.1.4rc1

Provider redis: 3.3.2rc1

Provider salesforce: 5.4.3rc1

Provider samba: 4.2.2rc1

Provider sftp: 4.6.1rc1

Provider slack: 8.1.0rc1

Provider smtp: 1.3.2rc1

Provider snowflake: 5.0.1rc1

Provider ssh: 3.7.3rc1

Provider tableau: 4.2.2rc1

Provider trino: 5.3.1rc1

Provider vertica: 3.5.2rc1

Provider zendesk: 4.3.2rc1

All users involved in the PRs:
@Taragolis @fabiogra @vijay-jangir @darkag @okayhooni @moiseenkov @RyuSA @potiuk @yermalov-here @eladkal @bkossakowska @hussein-awala @pankajastro @adam133 @kristopherkane @pankajkoti @melugoyal
@pierrejeambrun @JDarDagran @GeoffroyDFox @RNHTTR @mjsqu @dstandish @josh-fell @wolfdn @Lee-W

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 Sep 8, 2023
@yermalov-here
Copy link
Contributor

#33952 works as expected

@Taragolis
Copy link
Contributor

@melugoyal
Copy link
Contributor

#33715 works as expected

@JDarDagran
Copy link
Contributor

#34122 works fine
#33959 does not work properly, for DbtCloudRunJobOperator it raises:

[2023-09-08, 21:36:05 UTC] {base.py:152} ERROR - OpenLineage provider method failed to extract data from provider. 
Traceback (most recent call last):
  File "/usr/local/lib/python3.8/site-packages/airflow/providers/openlineage/extractors/base.py", line 137, in _get_openlineage_facets
    facets: OperatorLineage = get_facets_method(*args)
  File "/usr/local/lib/python3.8/site-packages/airflow/providers/dbt/cloud/operators/dbt.py", line 229, in get_openlineage_facets_on_complete
    return generate_openlineage_events_from_dbt_cloud_run(operator=self, task_instance=task_instance)
  File "/usr/local/lib/python3.8/site-packages/airflow/providers/dbt/cloud/utils/openlineage.py", line 60, in generate_openlineage_events_from_dbt_cloud_run
    run_id=operator.run_id, account_id=operator.account_id, include_related=["run_steps,job"]
AttributeError: 'DbtCloudRunJobOperator' object has no attribute 'run_id'

I'll raise an issue and try to solve this.

airflow-oss-bot added a commit to astronomer/astronomer-providers that referenced this issue Sep 9, 2023
@RNHTTR
Copy link
Contributor

RNHTTR commented Sep 9, 2023

#33685 doesn't work for @task decorated operators, but I don't think that's a big deal since I don't think these kinds of tasks by themselves are that useful for lineage data, so I think this one is fine. @mobuchowski what do you think?

@mobuchowski
Copy link
Contributor

@RNHTTR what if you disable _PythonDecoratedOperator?

@hussein-awala
Copy link
Member

I checked all my 101 changes, and they are all present in the RC.

@Lee-W
Copy link
Member

Lee-W commented Sep 10, 2023

Tested #33825, #33822, #34098

Will we be able to include documentation changes like #34104, #34103, #34102, #34101, #34097, #34096, #34095, #34094, #34074, #34073?

@pankajkoti
Copy link
Member

Tested my change #34018 in the Google RC 10.8.0rc1. It works fine, but, it also has a dependency on common-sql provider 1.7.2.rc1 for the change in same PR. If the common-sql provider is not updated then it fails. How do we handle cross-provider dependency bumps during releases? Does it get handled automatically or we need a manual minimum dependency bump here in Google RC to contain common-sql>=1.7.2?

@hussein-awala
Copy link
Member

it also has a dependency on common-sql provider 1.7.2.rc1 for the change in same PR. If the common-sql provider is not updated then it fails.

IMHO if the operator will be broken before upgrading the common-sql version to latest, then we should consider it as breaking change and fix it. The min version of common-sql is 1.3.1 in google provider, bumping it to 1.7.2 could fix the issue, and I think that it's safe as we still use the same major version.

@potiuk
Copy link
Member

potiuk commented Sep 10, 2023

Yep. We should bump min version of common-sql

@pankajkoti
Copy link
Member

pankajkoti commented Sep 10, 2023

Thank you @hussein-awala and @potiuk for your quick inputs and suggestions. I have created a PR now to bump the min version #34257.

cc: @eladkal Sorry din't realise this earlier. What would be the steps for releasing the Google RC now as it may depend on PR #34257?

@potiuk
Copy link
Member

potiuk commented Sep 11, 2023

Checked all my changes are in (mostly dependencies). All looks good.

@eladkal
Copy link
Contributor Author

eladkal commented Sep 11, 2023

dbt.cloud will be excluded from this wave due to issues found.
please keep testing rest of the providers

@mobuchowski
Copy link
Contributor

mobuchowski commented Sep 11, 2023

#33959 bug does not affect OpenLineage provider, just dbt one - we should only exclude this. I will doublecheck OL provider.

EDIT: #34270 should fix this issue, maybe release from RC2?

@moiseenkov
Copy link
Contributor

#34068 works fine

@darkag
Copy link
Contributor

darkag commented Sep 11, 2023

#34041 works as expected

@josh-fell
Copy link
Contributor

#34106 and #34130 look good!

@eladkal
Copy link
Contributor Author

eladkal commented Sep 12, 2023

#33959 bug does not affect OpenLineage provider, just dbt one - we should only exclude this. I will doublecheck OL provider.

EDIT: #34270 should fix this issue, maybe release from RC2?

I will cut rc2 for dbt.cloud

@eladkal
Copy link
Contributor Author

eladkal commented Sep 12, 2023

Thank you everyone.
dbt.cloud is excluded from this release. The rest of 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 Sep 12, 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