mattcasters opened a new pull request, #9108:
URL: https://github.com/apache/hop/pull/9108

   A failed statement leaves the caching database execution location on an 
aborted PostgreSQL session. Later writes then fail with `25P02`, or with 
`42P01` / `3F000` when that session no longer sees `hop_executions`, even 
though a new connection would succeed. The location already retried a closed 
connection. It now rolls the failed session back, drops it, and retries the 
write once. It does not try to commit an aborted transaction.
   
   addresses #9107
   
   `CachingDatabaseExecutionInfoLocationTest`: 24 tests, 0 failures. 
`apache-rat:check` was not run.
   
   ------------------------
   
   Thank you for your contribution! Follow this checklist to help us 
incorporate your contribution quickly and easily:
   - [ ] Run `mvn clean install apache-rat:check` to make sure basic checks 
pass. A more thorough check will be performed on your pull request 
automatically.
   - [x] If you have a group of commits related to the same change, please 
squash your commits into one and force push your branch using `git rebase -i`.
   - [x] Mention the appropriate issue in your description (for example: 
`addresses #123`), if applicable.
   
   To make clear that you license your contribution under the [Apache License 
Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0)
   you have to acknowledge this by using the following check-box.
   
   - [x] I hereby declare this contribution to be licensed under the [Apache 
License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0)
   - [ ] In any other case, please file an [Apache Individual Contributor 
License Agreement](https://www.apache.org/licenses/icla.pdf).
   


-- 
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]

Reply via email to