hadoop-hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul Yang (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HIVE-1335) DataNucleus should use connection pooling
Date Tue, 18 May 2010 03:38:42 GMT

    [ https://issues.apache.org/jira/browse/HIVE-1335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12868506#action_12868506

Paul Yang commented on HIVE-1335:

I applied the patch and ran 'ant ', but got this error


/trunk/VENDOR.hive/trunk] ant
Buildfile: build.xml






     [echo] Compiling: anttasks
    [javac] Compiling 2 source files to /data/users/pyang/task/trunk/VENDOR.hive/trunk/build/anttasks/classes

/data/users/pyang/task/trunk/VENDOR.hive/trunk/build.xml:159: The following error occurred
while executing this line:
/data/users/pyang/task/trunk/VENDOR.hive/trunk/build.xml:103: The following error occurred
while executing this line:
/data/users/pyang/task/trunk/VENDOR.hive/trunk/build-common.xml:369: The following error occurred
while executing this line:
/data/users/pyang/task/trunk/VENDOR.hive/trunk/ant/build.xml:40: /data/users/pyang/task/trunk/VENDOR.hive/trunk/build/ivy/lib/metastore/default
not found.


The error goes away if I do 'ant' under metastore/ first.

> DataNucleus should use connection pooling
> -----------------------------------------
>                 Key: HIVE-1335
>                 URL: https://issues.apache.org/jira/browse/HIVE-1335
>             Project: Hadoop Hive
>          Issue Type: Improvement
>    Affects Versions: 0.5.0
>            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-1.patch.txt, 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.

View raw message