I have a very peculiar problem.
For my clover ETL graphs , due to language support, i need to keep dbconnection as threadSafe=false in config properties file
However,this is causing a graph to look for a new DB connection everytime.
Now my graph has different phases, my doubt is
1) Does clover creates a new connection for each phase's db request - (As threadsafe=false, i think it should)
2) If it does, then is there a way to define the graph as threadSafe at phase level ? i.e. It may look for new DB connection when i run different graphs, but for a single graph for each phase it uses the same DB connection.
For my clover ETL graphs , due to language support, i need to keep dbconnection as threadSafe=false in config properties file
However,this is causing a graph to look for a new DB connection everytime.
Now my graph has different phases, my doubt is
1) Does clover creates a new connection for each phase's db request - (As threadsafe=false, i think it should)
2) If it does, then is there a way to define the graph as threadSafe at phase level ? i.e. It may look for new DB connection when i run different graphs, but for a single graph for each phase it uses the same DB connection.
-
Hello, varkashy,
as it is stated in your previous topic (http://forum.cloveretl.com/viewtopic.php?f=4&t=6430&sid=6cf72aba3c0f3d8ae7147e7318b79671), threadSafe=false means that graph tries to recycle one connection for each thread. Behavior when each thread has it's own connection equals to threadSafe=true. And there is no way how to combine these two settings at phase level. You can find more info here: http://doc.cloveretl.com/documentation/UserGuide/topic/com.cloveretl.gui.docs/docs/database-connection-wizard.html
Best regards,
Please sign in to leave a comment.
Comments 1