-
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 July 09, 2024 #40661
Comments
I checked all my changes they look good. One SMALL thing.. I noticed that weaviate changelog is wrong - the 2.0.0 changelog contains also 1.4.2 changes and 1.4.2 is missing from changelog. This is caused by #40194 - where |
I checked all my changes they look good. Thanks ! |
I checked Teradata airflow provider and new feature(s) are working as expected. Thank you!. |
I have checked all my changes they work as expected. |
I checked my change for the snowflake provider, it works as expected. |
Weaviate provider will have rc2 |
I checked all my changes on the Databricks operator; it works fine! |
I have tested #40642 and it is working. |
Ok for #40560 |
OK for ydb provider and #40390 |
Yes! |
Amazon provider will be excluded from rc1 |
Checked and working as expected. |
#40479 is ok |
I just found a serious problem in databricks provider. PR coming in a moment.
If PR 40153 is contained in the release then for sure we need to stop and a -1 from my side.
Sent from Outlook for iOS<https://aka.ms/o0ukef>
…________________________________
From: Aurelien Didier ***@***.***>
Sent: Wednesday, July 10, 2024 11:12:28 PM
To: apache/airflow ***@***.***>
Cc: Scheffler Jens (XC-AS/EAE-ADA-T) ***@***.***>; Mention ***@***.***>
Subject: Re: [apache/airflow] Status of testing Providers that were prepared on July 09, 2024 (Issue #40661)
#40518<#40518>
Checked and working as expected.
—
Reply to this email directly, view it on GitHub<#40661 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AWVTFDO7LONFW5AE4BDKVGLZLWPTZAVCNFSM6AAAAABKSHNSR6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMRRGQ4DEOBUGA>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Dont see my previous email, -1 for databricks, raised a fix PR #40708 but would rather recomment to roll back #40153
Sent from Outlook for iOS<https://aka.ms/o0ukef>
…________________________________
From: Elad Kalif ***@***.***>
Sent: Wednesday, July 10, 2024 6:32:10 PM
To: apache/airflow ***@***.***>
Cc: Scheffler Jens (XC-AS/EAE-ADA-T) ***@***.***>; Mention ***@***.***>
Subject: Re: [apache/airflow] Status of testing Providers that were prepared on July 09, 2024 (Issue #40661)
I will exclude fab from rc1
—
Reply to this email directly, view it on GitHub<#40661 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AWVTFDLUQO5ARSR2PFJPOR3ZLVOYVAVCNFSM6AAAAABKSHNSR6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMRQHE3TMNRVGM>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Ah, emails are getting to ticket and not to devlist :-D As far as I see the PR #40153 is not in the providers-cut? Then it is OK... |
yes, #40153 is not in this providers wave |
Yeah. Good catch @dabla -> I think it's not a blocker for this release, it's not a regression comparing to already released common.sql and we can always fix it in the next round (and it has rather small-ish impact). |
@dabla can you raise PR with a fix for it? |
Hey Elad, yes I already have a fix for it, but would like to see PR #40665 merged first as this will allow me to have a cleaner solution. Unless you want this fix first then I will have to refactor the fix in #40665 afterwards, that's also possible. It's up to you |
Similar answer :) |
Same for me, if you want the fix @eladkal, it can be done now/today... |
I already started with the PR for this fix, can merge #40665 afterwards, not such a big issue anyway |
Thank you everyone. Providers are released (excluding amazon and weaviate) I invite everyone to help improve providers for the next release, a list of open issues can be found here. |
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?
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 amazon: 8.26.0rc1
Linked issues:
Linked issues:
Linked issues:
Linked issues:
Provider cncf.kubernetes: 8.3.3rc1
Linked issues:
Provider common.sql: 1.14.2rc1
Provider databricks: 6.7.0rc1
Linked issues:
Linked issues:
Provider docker: 3.12.2rc1
Linked issues:
Provider fab: 1.2.1rc1
/logout
method (#40479): @shahar1Linked issues:
Provider google: 10.21.0rc1
GCSToGCSOperator
behavior difference for moving single object (#40162)" (#40577): @MaksYermakLinked issues:
Linked issues:
Provider influxdb: 2.6.0rc1
Linked issues:
Provider microsoft.azure: 10.2.0rc1
Provider openlineage: 1.9.1rc1
Provider oracle: 3.10.3rc1
Provider snowflake: 5.6.0rc1
Provider teradata: 2.4.0rc1
Provider weaviate: 2.0.0rc1
Provider ydb: 1.1.0rc1
All users involved in the PRs:
@BenediktRamsauer @marcel-martinelli @kacpermuda @uzhastik @jsjasonseba @antoinetavant @theopus @CYarros10 @sc250072 @MaksYermak @boraberke @guillaumeblaquiere @o-nikolas @Lee-W @shahar1 @potiuk @ellism
Committer
The text was updated successfully, but these errors were encountered: