-
Notifications
You must be signed in to change notification settings - Fork 14.4k
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 January 02, 2023 #28679
Comments
✅ for me, as our CI ran the example DAGs sucessfully, which include the newly introduced operators/sensors. |
#28108 is a document-only change (docs build successfully) |
#28617 also looks good on my local, anyway it is a small change |
All Good:
I had no hive and connection defined, but it was correctly added and used by JINJA and was clearly taken from hive provider, not airflow core:
Also it is visible in Airflow Webserver as Plugin when the new hive provider is installed (missing when installing hive provider 5.0.0): |
#28555: This only affect CI and it pass #28507, #27775, #27858: Working fine #28279: Check on AWS environment, work fine #28505 - @potiuk I've found that we try to import airflow/airflow/providers/amazon/aws/transfers/sql_to_s3.py Lines 25 to 32 in 8cb69bb
File "/opt/airflow/dags/example_aws.py", line 5, in <module>
from airflow.providers.amazon.aws.transfers.sql_to_s3 import SqlToS3Operator
File "/home/airflow/.local/lib/python3.9/site-packages/airflow/providers/amazon/aws/transfers/sql_to_s3.py", line 25, in <module>
import numpy as np
ModuleNotFoundError: No module named 'numpy' |
I don't think this is a concern... |
Agree. It's just "less clear" exception in this case, not a blocker for sure. But I will add a fix for the next version. |
Yeah agree can do it later. This kind of import only critical if it optional part of Hooks, not a operators. We could just move it inside |
#27893 all good with a integration test: |
Tested #28235 and it looks good, thanks! |
Thank you everyone. |
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.0.0rc2
create_job_kwargs
arg (#28403): @IAL32AwsLambdaInvokeFunctionOperator
(#28233): @eladkalpass
statement in conditions (#27775): @Taragolis^
conditions byexactly_one
helper in providers (#27858): @TaragolisProvider apache.hive: 5.1.0rc2
Provider atlassian.jira: 2.0.0rc2
Provider cncf.kubernetes: 5.1.0rc2
Provider common.sql: 1.3.2rc2
Provider docker: 3.4.0rc2
Provider elasticsearch: 4.3.2rc2
Provider ftp: 3.3.0rc2
FTPFileTransmitOperator
(#26974): @RachitSharma2001Provider google: 8.7.0rc2
pylint
messages control instructions (#28555): @Taragolispass
statement in conditions (#27775): @Taragolis^
conditions byexactly_one
helper in providers (#27858): @TaragolisProvider imap: 3.1.1rc2
pass
statement in conditions (#27775): @TaragolisProvider microsoft.azure: 5.0.2rc2
Provider microsoft.mssql: 3.3.2rc2
pymsql
on ARM as it now builds cleanly (#28530): @TaragolisProvider microsoft.winrm: 3.1.1rc2
Provider oracle: 3.6.0rc2
Provider postgres: 5.4.0rc2
Provider presto: 4.2.1rc2
Provider salesforce: 5.3.0rc2
Provider sftp: 4.2.1rc2
pass
statement in conditions (#27775): @TaragolisProvider slack: 7.1.1rc2
^
conditions byexactly_one
helper in providers (#27858): @TaragolisProvider ssh: 3.4.0rc2
pass
statement in conditions (#27775): @TaragolisProvider telegram: 3.1.1rc2
Provider trino: 4.3.1rc2
The guidelines on how to test providers can be found in
Verify providers by contributors
All users involved in the PRs:
@Taragolis @syedahsn @xinbinhuang @vchiapaikeo @ferruzzi @jon-evergreen @RachitSharma2001 @syun64 @snjypl @pankajastro @thangnd197 @dwreeves @eladkal @KarshVashi @BobDu @hankehly @xjf729 @Adityamalik123
@jbandoro @IAL32 @lwyszomi @moiseenkov @VladaZakharova @stamixthereal @vincbeck @2h-kim @kolfild26 @potiuk @raphaelauv @TohnJhomas @dstandish @vandonr-amz @romibuzi @mdering @skabbit @odaneau-astro
@kouk
Committer
The text was updated successfully, but these errors were encountered: