You are viewing a plain text version of this content. The canonical link for it is here.

Posted to user@mahout.apache.org by Aleksei Udatšnõi <a....@gmail.com> on 2011/10/31 09:53:08 UTC

Non-standard ConnectionPoolDataSource

I noticed that Mahout has its version of ConnectionPoolDataSource
class. It somewhat conflicts with javax.sql.ConnectionPoolDataSource
interface and its implementations like
com.mysql.jdbc.jdbc2.optional.MysqlConnectionPoolDataSource.

For example, if I set up my pooled JNDI connection using
MysqlConnectionPoolDataSource, Mahout still generates a warning about
"You are not using ConnectionPoolDataSource ..". That's because Mahout
only expects the instances of its own ConnectionPoolDataSource to be
used.

So which of these pooled connection classes would you recommend to use
in Mahout?

Thanks,
Aleksei

Re: Non-standard ConnectionPoolDataSource

Posted by Sebastian Schelter <ss...@apache.org>.

You can ignore this warning and use a connection pool of your choice.
The warning is just a reminder to use pooling in general.

--sebastian

On 31.10.2011 09:53, Aleksei Udatšnõi wrote:
> I noticed that Mahout has its version of ConnectionPoolDataSource
> class. It somewhat conflicts with javax.sql.ConnectionPoolDataSource
> interface and its implementations like
> com.mysql.jdbc.jdbc2.optional.MysqlConnectionPoolDataSource.
> 
> For example, if I set up my pooled JNDI connection using
> MysqlConnectionPoolDataSource, Mahout still generates a warning about
> "You are not using ConnectionPoolDataSource ..". That's because Mahout
> only expects the instances of its own ConnectionPoolDataSource to be
> used.
> 
> So which of these pooled connection classes would you recommend to use
> in Mahout?
> 
> Thanks,
> Aleksei