[jira] Commented: (HIVE-1335) DataNucleus should use connection pooling

2010-05-27 Thread He Yongqiang (JIRA)

[ 
https://issues.apache.org/jira/browse/HIVE-1335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12872376#action_12872376
 ] 

He Yongqiang commented on HIVE-1335:


It seems this introduced an error msg?


heyongqiangMBP:Hive-Index heyongqiang$ ant test -Dtestcase=TestCliDriver
Buildfile: build.xml

BUILD FAILED
/Users/heyongqiang/Documents/workspace/Hive-Index/build.xml:112: fileset 
doesn't support the erroronmissingdir attribute



 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-2.patch.txt, hive-1335-3.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.



[jira] Commented: (HIVE-1335) DataNucleus should use connection pooling

2010-05-27 Thread John Sichi (JIRA)

[ 
https://issues.apache.org/jira/browse/HIVE-1335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12872378#action_12872378
 ] 

John Sichi commented on HIVE-1335:
--

@Yongqiang:  Per Paul's instructions, you need to upgrade to ant 1.8.1


 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-2.patch.txt, hive-1335-3.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.



[jira] Commented: (HIVE-1335) DataNucleus should use connection pooling

2010-05-27 Thread Paul Yang (JIRA)

[ 
https://issues.apache.org/jira/browse/HIVE-1335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12872379#action_12872379
 ] 

Paul Yang commented on HIVE-1335:
-

This patch makes ant 1.7.1 or higher required. I'll send you an email on how to 
update our internal build.

 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-2.patch.txt, hive-1335-3.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.



[jira] Commented: (HIVE-1335) DataNucleus should use connection pooling

2010-05-24 Thread Paul Yang (JIRA)

[ 
https://issues.apache.org/jira/browse/HIVE-1335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12870722#action_12870722
 ] 

Paul Yang commented on HIVE-1335:
-

Sorry, about that - missed the update email.

Looks good +1

 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-2.patch.txt, hive-1335-3.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.



[jira] Commented: (HIVE-1335) DataNucleus should use connection pooling

2010-05-24 Thread Namit Jain (JIRA)

[ 
https://issues.apache.org/jira/browse/HIVE-1335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12870755#action_12870755
 ] 

Namit Jain commented on HIVE-1335:
--

John, can you commit this one ?

 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-2.patch.txt, hive-1335-3.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.



[jira] Commented: (HIVE-1335) DataNucleus should use connection pooling

2010-05-24 Thread Namit Jain (JIRA)

[ 
https://issues.apache.org/jira/browse/HIVE-1335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12870782#action_12870782
 ] 

Namit Jain commented on HIVE-1335:
--

Since John is still having problems with the committer access, I will commit 
this if the tests pass

 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-2.patch.txt, hive-1335-3.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.



[jira] Commented: (HIVE-1335) DataNucleus should use connection pooling

2010-05-23 Thread Edward Capriolo (JIRA)

[ 
https://issues.apache.org/jira/browse/HIVE-1335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12870477#action_12870477
 ] 

Edward Capriolo commented on HIVE-1335:
---

Can we go +1?

 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-2.patch.txt, hive-1335-3.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.



[jira] Commented: (HIVE-1335) DataNucleus should use connection pooling

2010-05-18 Thread Paul Yang (JIRA)

[ 
https://issues.apache.org/jira/browse/HIVE-1335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12868979#action_12868979
 ] 

Paul Yang commented on HIVE-1335:
-

One last thing, can you do something like

{code}
fileset file=${build.dir.hive}/ivy/lib/metastore/default/commons-dbcp-*.jar/
fileset file=${build.dir.hive}/ivy/lib/metastore/default/commons-pool-*.jar/
fileset 
file=${build.dir.hive}/ivy/lib/metastore/default/datanucleus-connectionpool-*.jar/
{code}

instead of having the specific version numbers?

 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-2.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.



[jira] Commented: (HIVE-1335) DataNucleus should use connection pooling

2010-05-14 Thread Edward Capriolo (JIRA)

[ 
https://issues.apache.org/jira/browse/HIVE-1335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12867538#action_12867538
 ] 

Edward Capriolo commented on HIVE-1335:
---

Just a strange side-note. Why is the classpath specified in both build.xml and 
build-common.xml. Do we need it defined in both places?

 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.



[jira] Commented: (HIVE-1335) DataNucleus should use connection pooling

2010-05-05 Thread Edward Capriolo (JIRA)

[ 
https://issues.apache.org/jira/browse/HIVE-1335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12864564#action_12864564
 ] 

Edward Capriolo commented on HIVE-1335:
---

{noformat}
[ivy:resolve] :: Ivy 2.1.0 - 20090925235825 :: http://ant.apache.org/ivy/ ::
[ivy:resolve] :: loading settings :: file = 
/mnt/data/hive/hive/ivy/ivysettings.xml
[ivy:resolve] 
[ivy:resolve] :: problems summary ::
[ivy:resolve]  WARNINGS
[ivy:resolve]   module not found: proxool#proxool;0.9.0RC3
[ivy:resolve]    hadoop-source: tried
[ivy:resolve] -- artifact proxool#proxool;0.9.0RC3!proxool.jar:
[ivy:resolve] 
http://mirror.facebook.net/facebook/hive-deps/hadoop/core/proxool-0.9.0RC3/proxool-0.9.0RC3.jar
[ivy:resolve]    apache-snapshot: tried
[ivy:resolve] 
https://repository.apache.org/content/repositories/snapshots/proxool/proxool/0.9.0RC3/proxool-0.9.0RC3.pom
[ivy:resolve] -- artifact proxool#proxool;0.9.0RC3!proxool.jar:
[ivy:resolve] 
https://repository.apache.org/content/repositories/snapshots/proxool/proxool/0.9.0RC3/proxool-0.9.0RC3.jar
[ivy:resolve]    maven2: tried
[ivy:resolve] 
http://repo1.maven.org/maven2/proxool/proxool/0.9.0RC3/proxool-0.9.0RC3.pom
[ivy:resolve] -- artifact proxool#proxool;0.9.0RC3!proxool.jar:
[ivy:resolve] 
http://repo1.maven.org/maven2/proxool/proxool/0.9.0RC3/proxool-0.9.0RC3.jar
[ivy:resolve]   ::
[ivy:resolve]   ::  UNRESOLVED DEPENDENCIES ::
[ivy:resolve]   ::
[ivy:resolve]   :: proxool#proxool;0.9.0RC3: not found
[ivy:resolve]   ::
[ivy:resolve] 
[ivy:resolve] :: USE VERBOSE OR DEBUG MESSAGE LEVEL FOR MORE DETAILS
{noformat}

Lol wonderful. After ivy decides to go after a bunch of things I do not really 
need, and of course one of them fails. The future is here.

 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.



[jira] Commented: (HIVE-1335) DataNucleus should use connection pooling

2010-05-05 Thread John Sichi (JIRA)

[ 
https://issues.apache.org/jira/browse/HIVE-1335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12864569#action_12864569
 ] 

John Sichi commented on HIVE-1335:
--

Heh, whoops, looks like they made datanucleus-connectionpool depend on every 
available pool implentation (plus datanucleus itself).  There may be a way to 
tell it to fetch just datanucleus-connectionpool without its dependencies.


 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.



[jira] Commented: (HIVE-1335) DataNucleus should use connection pooling

2010-05-05 Thread Edward Capriolo (JIRA)

[ 
https://issues.apache.org/jira/browse/HIVE-1335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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.



[jira] Commented: (HIVE-1335) DataNucleus should use connection pooling

2010-05-05 Thread John Sichi (JIRA)

[ 
https://issues.apache.org/jira/browse/HIVE-1335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12864629#action_12864629
 ] 

John Sichi commented on HIVE-1335:
--

If you use these settings, you'll get exactly what you're after:

{noformat}
ivy-module version=2.0
info organisation=org.apache.hadoop.hive module=metastore/
dependencies
dependency org=hadoop name=core 
rev=${hadoop.version.ant-internal}
  artifact name=hadoop type=source ext=tar.gz/
/dependency 
dependency org=commons-dbcp name=commons-dbcp rev=1.2.2
  exclude module=commons-pool /
/dependency
dependency org=commons-pool name=commons-pool rev=1.2
  exclude module=commons-collections /
  exclude module=xerces /
  exclude module=xml-apis /
/dependency
dependency org=org.datanucleus name=datanucleus-connectionpool 
rev=1.0.2
  exclude module=proxool /
  exclude module=c3p0 /
  exclude module=datanucleus-core /
  exclude module=datanucleus-rdbms /
  exclude module=commons-collections /
  exclude module=commons-pool /
/dependency
/dependencies
/ivy-module

jsichi-mac:metastore jsichi$ ant ivy-retrieve
Buildfile: build.xml

ivy-init-dirs:

ivy-download:
  [get] Getting: 
http://repo2.maven.org/maven2/org/apache/ivy/ivy/2.1.0/ivy-2.1.0.jar
  [get] To: /Users/jsichi/open/hive-trunk/build/ivy/lib/ivy-2.1.0.jar
  [get] Not modified - so not downloaded

ivy-probe-antlib:

ivy-init-antlib:

ivy-init:

ivy-resolve:
[ivy:resolve] :: Ivy 2.1.0 - 20090925235825 :: http://ant.apache.org/ivy/ ::
[ivy:resolve] :: loading settings :: file = 
/Users/jsichi/open/hive-trunk/ivy/ivysettings.xml
[ivy:resolve] downloading 
http://repo1.maven.org/maven2/commons-dbcp/commons-dbcp/1.2.2/commons-dbcp-1.2.2.jar
 ...
[ivy:resolve] .
[ivy:resolve] . (118kB)
[ivy:resolve] .. (0kB)
[ivy:resolve]   [SUCCESSFUL ] commons-dbcp#commons-dbcp;1.2.2!commons-dbcp.jar 
(3271ms)
[ivy:resolve] downloading 
http://repo1.maven.org/maven2/commons-pool/commons-pool/1.2/commons-pool-1.2.jar
 ...
[ivy:resolve] ... (41kB)
[ivy:resolve] .. (0kB)
[ivy:resolve]   [SUCCESSFUL ] commons-pool#commons-pool;1.2!commons-pool.jar 
(2412ms)
[ivy:resolve] downloading 
http://repo1.maven.org/maven2/org/datanucleus/datanucleus-connectionpool/1.0.2/datanucleus-connectionpool-1.0.2.jar
 ...
[ivy:resolve]  (14kB)
[ivy:resolve] .. (0kB)
[ivy:resolve]   [SUCCESSFUL ] 
org.datanucleus#datanucleus-connectionpool;1.0.2!datanucleus-connectionpool.jar 
(2683ms)

ivy-retrieve:

BUILD SUCCESSFUL
{noformat}

Personally, I agree that the cost/benefit of ivy is shaky, but if Hive as a 
project has chosen it, then we should use it where possible.  If that decision 
needs to be revisited, then it would be good to resolve that.


 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.



[jira] Commented: (HIVE-1335) DataNucleus should use connection pooling

2010-05-03 Thread Paul Yang (JIRA)

[ 
https://issues.apache.org/jira/browse/HIVE-1335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12863527#action_12863527
 ] 

Paul Yang commented on HIVE-1335:
-

Can you add *.LICENSE files?

 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-pool-1.2.jar, 
 datanucleus-connectionpool-1.0.2.jar, 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.



[jira] Commented: (HIVE-1335) DataNucleus should use connection pooling

2010-05-03 Thread John Sichi (JIRA)

[ 
https://issues.apache.org/jira/browse/HIVE-1335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12863531#action_12863531
 ] 

John Sichi commented on HIVE-1335:
--

Should we use ivy for the new dependencies?


 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-pool-1.2.jar, 
 datanucleus-connectionpool-1.0.2.jar, 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.



[jira] Commented: (HIVE-1335) DataNucleus should use connection pooling

2010-05-03 Thread John Sichi (JIRA)

[ 
https://issues.apache.org/jira/browse/HIVE-1335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12863552#action_12863552
 ] 

John Sichi commented on HIVE-1335:
--

http://ant.apache.org/ivy/history/latest-milestone/tutorial/start.html

So, in metastore/ivy.xml, you can declare a dependency like this:

dependency org=commons-dbcp name=commons-dbcp rev=1.2.2/

Search here for the other modules:

http://mvnrepository.com/

Then metastore/build.xml needs to invoke ivy-retrieve from some target, maybe 
compile?


 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.