[
https://issues.apache.org/jira/browse/HIVE-1335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12864622#action_12864622
]
Edward Capriolo commented on HIVE-1335:
---------------------------------------
No joy.
{noformat}
+ <dependency org="commons-dbcp" name="commons-dbcp" rev="1.2.2"/>
+ <dependency org="commons-pool" name="commons-pool" rev="1.2"/>
+ <dependency org="org.datanucleus" name="datanucleus-connectionpool"
rev="1.0.2">
+ <exclude module="proxool" />
+ <exclude module="c3p0" />
+ </dependency>
{noformat}
Unfortunately the datanucleus-connectpool refuses to honor my request for
commons-pool 1.2 and instead fetches 1.3, which ,you guest it, does not work. I
am going to submit the original, figuring out what ivy is trying to do is
taking too long.
> DataNucleus should use connection pooling
> -----------------------------------------
>
> Key: HIVE-1335
> URL: https://issues.apache.org/jira/browse/HIVE-1335
> Project: Hadoop Hive
> Issue Type: Improvement
> Reporter: Edward Capriolo
> Assignee: Edward Capriolo
> Fix For: 0.6.0
>
> Attachments: commons-dbcp-1.2.2.jar, commons-dbcp.LICENSE,
> commons-pool-1.2.jar, commons-pool.LICENSE,
> datanucleus-connectionpool-1.0.2.jar, datanucleus-connectionpool.LICENSE,
> hive-1335.patch.txt
>
>
> Currently each Data Nucleus operation disconnects and reconnects to the
> MetaStore over jdbc. Queries fail to even explain properly in cases where a
> table has many partitions. This is fixed by enabling one parameter and
> including several jars.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
