-
Notifications
You must be signed in to change notification settings - Fork 14.5k
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 05, 2022 #21348
Comments
docker operator is buggy even with DockerOperator(
task_id='docker_op_tester',
dag=dag,
api_version='auto',
docker_url="unix://var/run/docker.sock",
command='/bin/echo tata',
image='centos:latest',
network_mode='bridge',
mount_tmp_dir=False,
do_xcom_push=True,
) fail with
|
#19787 requires one additional fix in here: Without this fix, it becomes inconsistent with the logic changed in the airflow/providers/amazon/aws/hooks/glue.py. It then gives the error to the user if user doesn't specify
|
Ok. Still worth testing Amazon changes on this version but I will remove Amazon + Docker (if confirmed) and prepare RC2 right after we release all others and get fixes merged. Thanks @Ritika-Singhal @raphaelauv ! |
I also removed some of the "no-need-to-test" changes (and 2.6.0 amazon changes - which was a bug in generation of the issue - sorry for that. |
Good question. Depends on your "local" environment. But what I would do, is to use:
This will start our dockerized development environment with Airflow 2.2.3 installed and open 4 terminals: triggerer, scheduler, webserver and "bash console".
In the console:
Then restarting scheduler/webserver (by Ctrl+C) followed by "up cursor" to go back and run previous command
For that you likely need to configure the "google_default_connection" to include your credentials. You can put your dags in "files/dags" folder of your Airlfow sources (the "files" folder is mounted to inside the docker) and they should be scanned/visible in webserver |
@potiuk – Oracle and PSRP providers all good. |
@potiuk Part of #21237 was adding 3 new lexers for the SQL rendering in the UI. For the providers that use the new lexers, the rendering won't be as readable as it could be because the configured lexer doesn't exist yet (i.e. the rendering becomes a Python type rendering). Do we want to wait on releasing #21237 at all until those lexers are available or not push the SQL For example, there is a new |
Good point Josh. I think this one might be a bit tricky, I do not think it is "blocker" - the rendering is not nice but it does not "break" anything. However I thought it might be a nice way to incentivize people to migrate to 2.2.4 if we also cherry-pick the lexer to 2.2.4. Then we could telll them "migrate to 2.2.4 to get it nicer". This is a new feature - of course - so technically we shoud add it in 2.3.0. So I am a bit torn here. There are quite a number of those providers that are only released because of this renderer so we can easily skip them from this release and release them when we release 2.3.0 |
The second option is to indeed drop all the "21237" providers an release them in RC2 with some "conditional" code that will check if the lexer is there. After thinking a bit I think that would be much "cleaner" solution and I am leaning towards this option. smth like:
|
I'd rather not include it for 2.2.4 since, as you said, it's a new feature. Doing it conditionally, until the next lower bound bump, I think makes sense. |
Yeah. It's easy enough to fix and I agree it's better. I think - due to the the number of those affected, it makes more sense to cancel the whole release and re-release all providers as RC2 with that fix to not mess with two releases. there are no super-urgent changes in this wave. |
As discussed above ^^ I will cancel the whole vote/release and will make an RC2 as soon as we release the conditonally working SQL renderer. Thanks @josh-fell for spotting this and raising it! |
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: 3.0.0rc1
EmrClusterLink
in deprecated AWS module (#21195): @josh-fellProvider apache.druid: 2.3.0rc1
Provider apache.hive: 2.2.0rc1
Provider apache.spark: 2.1.0rc1
Provider apache.sqoop: 2.1.0rc1
Provider cncf.kubernetes: 3.0.2rc1
Provider docker: 2.4.1rc1
Provider exasol: 2.1.0rc1
Provider google: 6.4.0rc1
GCSToLocalFilesystemOperator
to fix #20901 (#20919): @danneaves-eeProvider http: 2.0.3rc1
Provider imap: 2.2.0rc1
Provider jdbc: 2.1.0rc1
Provider microsoft.azure: 3.6.0rc1
Provider microsoft.mssql: 2.1.0rc1
Provider microsoft.psrp: 1.1.0rc1
Provider mysql: 2.2.0rc1
(Refactor vertica_to_mysql to make it more 'mypy' friendly #20618): @potiuk
Provider oracle: 2.2.0rc1
Provider postgres: 3.0.0rc1
:type
lines now sphinx-autoapi supports typehints (#20951): @ashbProvider qubole: 2.1.0rc1
Provider slack: 4.2.0rc1
(Fix template_fields type to have MyPy friendly Sequence type #20571): @potiuk
Provider snowflake: 2.5.0rc1
Provider sqlite: 2.1.0rc1
Provider ssh: 2.4.0rc1
Provider tableau: 2.1.4rc1
Provider vertica: 2.1.0rc1
Committer
The text was updated successfully, but these errors were encountered: