darkag opened a new issue, #32993: URL: https://github.com/apache/airflow/issues/32993
### Apache Airflow version 2.6.3 ### What happened Hello, There is a problem with multi-statement query and vertica, error will be detected only if it happens on the first statement of the sql. for example if I run the following sql with default SQLExecuteQueryOperator options: INSERT INTO MyTable (Key, Label) values (1, 'test 1'); INSERT INTO MyTable (Key, Label) values (1, 'test 2'); INSERT INTO MyTable (Key, Label) values (3, 'test 3'); the first insert will be commited, the nexts won't and no errors will be returned. the same sql runed on mysql will return an error and no row will be inserted. It seems to be linked to the way the vertica python client works (an issue has been opened on their git 4 years ago, [Duplicate key values error is not thrown as exception and is getting ignored](https://github.com/vertica/vertica-python/issues/255)) but since a workaround was provided I don't think it will be fixed in a near future. For the moment, to workaroud I use the split statement option with disabling auto-commit but I think it's dangerous to let this behaviour as is. ### What you think should happen instead _No response_ ### How to reproduce create a table MyTable with two columns Key and Lbl, declare Key as primary key. Run the following query with SQLExecuteQueryOperator INSERT INTO MyTable (Key, Label) values (1, 'test 1'); INSERT INTO MyTable (Key, Label) values (1, 'test 2'); INSERT INTO MyTable (Key, Label) values (3, 'test 3'); ### Operating System Debian GNU/Linux 11 (bullseye) ### Versions of Apache Airflow Providers _No response_ ### Deployment Official Apache Airflow Helm Chart ### Deployment details _No response_ ### Anything else _No response_ ### Are you willing to submit PR? - [ ] Yes I am willing to submit a PR! ### Code of Conduct - [X] I agree to follow this project's [Code of Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
