I stopped reading at JNDI ☺
You received this message because you are subscribed to the Google Groups "kettle-developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kettle-develop...@googlegroups.com.
To post to this group, send email to kettle-d...@googlegroups.com.
Visit this group at http://groups.google.com/group/kettle-developers.
For more options, visit https://groups.google.com/d/optout.
People constantly tell me about the problems they have with JNDI but they rarely change to regular JDBC connections in Kettle. Go figure ☺
Sound like you're having a lot of fun AND succes. Thanks for sharing your story Brandon, I really appreciate it.
Connection pooling would also be possible on a job level for the duration of the job. That's why it's beneficial to organise loops, queues and the like in a job (repeat option etc) or even better in a transformation. JNDI then doesn't really matter in those cases. If you have 3rd party software calling the shots it gets really hard to reduce the number of connections made.