Yes, this is the right way for the DIH. You might find it easier to write a separate local client that polls the DB and uploads changes. The DIH is oriented toward longer batch jobs.
On Thu, May 24, 2012 at 7:29 AM, Esteban Donato <esteban.don...@gmail.com> wrote: > Hi community, > > I am using Solr with DIH to index content from a DB. The point is > that I have to configure DIH to check changes in the DB very > frequently (aprox 1 sec) to maintain the index almost up-to-date. I > noted that JDBCDataSource closes the DB connection after every > execution which is not acceptable with this update rate. Ideally I > would need DIH using a connection pool. Looking at DIH code and faq I > noticed that I can configure a connection pool and expose it via jndi > for the JDBCDataSource to use it. My question is: is this they way to > go for integrating a connection pool with DIH? > > Thanks > Esteban -- Lance Norskog goks...@gmail.com
