dave-csc commented on issue #4751: URL: https://github.com/apache/hop/issues/4751#issuecomment-2604944132
Joining this discussion, since I had a similar issue. In may case the absence of connection pooling has caused a sort of temporary ban in a remote database, since I was making too many connections in a relatively short time (i.e. the time needed to get the results of a SELECT query...): after 2-3 queries my workflow deadlocked with no information in the logs. To workaround this, I grouped the query-related pipelines in a new pipeline and set the Run configuration as transactional for the latter one. It worked for my needs since I had to do SELECTs only. The case above can indeed be considered an added value for connection pooling. Also, it seems it's not currently possible to close a database transaction, but keeping the connection alive for other queries... -- 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]
