-
Notifications
You must be signed in to change notification settings - Fork 14.2k
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
PL/SQL statement stop working after upgrade common-sql to 1.1.0 #25851
Comments
cc: @kazanzhy - > will you take a look at that one or should I attempt to fix it ? I think having optional "strip_semicolon" and setting it to False by default in Oracle, should solve the issue. |
I also thought about the |
Yes @kazanzhy , every statement has a semicolon at the end, and after END too |
It will be great if you have a look at #25855 and help me to test it. |
@kazanzhy I want to test it, but the last version of common-sql is 1.1.0 how can I test this update? |
You can BYOP (build your own provider):
The .whl package should be prepared in your
|
(you need to have |
@potiuk I builded the package and installed in my container with airflow, it worked!
😄 |
Fantastic! thanks for confirmation! It's already merged and will go out in the next wave of providers :). Thanks @kazanzhy also for very quickl fixing ot that one :) |
Apache Airflow Provider(s)
common-sql, oracle
Versions of Apache Airflow Providers
apache-airflow-providers-common-sql==1.1.0
apache-airflow-providers-oracle==3.3.0
Apache Airflow version
2.3.3
Operating System
Debian GNU/Linux 11 (bullseye)
Deployment
Docker-Compose
Deployment details
No response
What happened
After upgrade provider common-sql==1.0.0 to 1.1.0 version, SQL with DECLARE stop working.
Using OracleProvider 3.2.0 with common-sql 1.0.0:
After upgrade OracleProvider to 3.3.0 with common-sql to 1.1.0 version, same statement now throws an exception:
What you think should happen instead
I think stripping
;
from statement is causing this errorHow to reproduce
No response
Anything else
No response
Are you willing to submit PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: