It is better to use re-use the hive jdbc connection if possible, as
there are costs associated with creating new connection. However,
there are known issues in running multiple queries simultaneously
using a single connection. For now, it woudl be safer to run queries
sequentially within a connection (ie, don't share it across threads
and run concurrent queries). (You can ofcourse run queries in parallel
using different connections).

Regarding connection pooling libraries, I am not sure if that has been
tested. There might be issues like that unsupported api call you
mentioned, that need to be fixed.

On Fri, Jun 5, 2015 at 6:50 AM, McWhorter, David
<[EMAIL PROTECTED]> wrote:
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB