from:"rohithsharma \(JIRA\)"


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

rohithsharma commented on HIVE-4633:


Complete exception trace is as below

{noformat}
Diagnostic Messages for this Task:
Error: java.lang.RuntimeException: Error in configuring object
at 
org.apache.hadoop.util.ReflectionUtils.setJobConf(ReflectionUtils.java:106)
at 
org.apache.hadoop.util.ReflectionUtils.setConf(ReflectionUtils.java:72)
at 
org.apache.hadoop.util.ReflectionUtils.newInstance(ReflectionUtils.java:130)
at org.apache.hadoop.mapred.MapTask.runOldMapper(MapTask.java:402)
at org.apache.hadoop.mapred.MapTask.run(MapTask.java:335)
at org.apache.hadoop.mapred.YarnChild$2.run(YarnChild.java:154)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:396)
at 
org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1232)
at org.apache.hadoop.mapred.YarnChild.main(YarnChild.java:149)
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at 
org.apache.hadoop.util.ReflectionUtils.setJobConf(ReflectionUtils.java:103)
... 9 more
Caused by: java.lang.RuntimeException: Error in configuring object
at 
org.apache.hadoop.util.ReflectionUtils.setJobConf(ReflectionUtils.java:106)
at 
org.apache.hadoop.util.ReflectionUtils.setConf(ReflectionUtils.java:72)
at 
org.apache.hadoop.util.ReflectionUtils.newInstance(ReflectionUtils.java:130)
at org.apache.hadoop.mapred.MapRunner.configure(MapRunner.java:38)
... 14 more
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at 
org.apache.hadoop.util.ReflectionUtils.setJobConf(ReflectionUtils.java:103)
... 17 more
Caused by: java.lang.RuntimeException: Map operator initialization failed
at 
org.apache.hadoop.hive.ql.exec.ExecMapper.configure(ExecMapper.java:121)
... 22 more
Caused by: org.apache.hadoop.hive.ql.metadata.HiveException: 
org.apache.hadoop.hive.ql.metadata.HiveException: Configuration and input path 
are inconsistent
at 
org.apache.hadoop.hive.ql.exec.MapOperator.setChildren(MapOperator.java:522)
at 
org.apache.hadoop.hive.ql.exec.ExecMapper.configure(ExecMapper.java:90)
... 22 more
Caused by: org.apache.hadoop.hive.ql.metadata.HiveException: Configuration and 
input path are inconsistent
at org.apache.hadoop.hive.q
{noformat}

 MR Jobs execution failed.
 -

 Key: HIVE-4633
 URL: https://issues.apache.org/jira/browse/HIVE-4633
 Project: Hive
  Issue Type: Bug
  Components: Query Processor
Affects Versions: 0.11.0
 Environment: Hive-0.11.0 + Hadoop-0.23 
Reporter: rohithsharma
Priority: Critical

 I am running Hive-0.11.0 + Hadoop-0.23 version. All queries that spawn MR 
 jobs got failed. When I look into logs, below exception is thrown in hive.log
 {noformat}
 Caused by: org.apache.hadoop.hive.ql.metadata.HiveException: 
 org.apache.hadoop.hive.ql.metadata.HiveException: Configuration and input 
 path are inconsistent
   at 
 org.apache.hadoop.hive.ql.exec.MapOperator.setChildren(MapOperator.java:522)
   at 
 org.apache.hadoop.hive.ql.exec.ExecMapper.configure(ExecMapper.java:90)
 {noformat}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (HIVE-4633) MR Jobs execution failed.

rohithsharma created HIVE-4633:
--

 Summary: MR Jobs execution failed.
 Key: HIVE-4633
 URL: https://issues.apache.org/jira/browse/HIVE-4633
 Project: Hive
  Issue Type: Bug
  Components: Query Processor
Affects Versions: 0.11.0
 Environment: Hive-0.11.0 + Hadoop-0.23 
Reporter: rohithsharma
Priority: Critical


I am running Hive-0.11.0 + Hadoop-0.23 version. All queries that spawn MR jobs 
got failed. When I look into logs, below exception is thrown in hive.log

{noformat}
Caused by: org.apache.hadoop.hive.ql.metadata.HiveException: 
org.apache.hadoop.hive.ql.metadata.HiveException: Configuration and input path 
are inconsistent
at 
org.apache.hadoop.hive.ql.exec.MapOperator.setChildren(MapOperator.java:522)
at 
org.apache.hadoop.hive.ql.exec.ExecMapper.configure(ExecMapper.java:90)
{noformat}




--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HIVE-4633) MR Jobs execution failed.


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

rohithsharma commented on HIVE-4633:


It is working fine with patch :-) I duplicate this defect. 

 MR Jobs execution failed.
 -

 Key: HIVE-4633
 URL: https://issues.apache.org/jira/browse/HIVE-4633
 Project: Hive
  Issue Type: Bug
  Components: Query Processor
Affects Versions: 0.11.0
 Environment: Hive-0.11.0 + Hadoop-0.23 
Reporter: rohithsharma
Priority: Critical

 I am running Hive-0.11.0 + Hadoop-0.23 version. All queries that spawn MR 
 jobs got failed. When I look into logs, below exception is thrown in hive.log
 {noformat}
 Caused by: org.apache.hadoop.hive.ql.metadata.HiveException: 
 org.apache.hadoop.hive.ql.metadata.HiveException: Configuration and input 
 path are inconsistent
   at 
 org.apache.hadoop.hive.ql.exec.MapOperator.setChildren(MapOperator.java:522)
   at 
 org.apache.hadoop.hive.ql.exec.ExecMapper.configure(ExecMapper.java:90)
 {noformat}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (HIVE-4633) MR Jobs execution failed.


 [ 
https://issues.apache.org/jira/browse/HIVE-4633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

rohithsharma resolved HIVE-4633.


Resolution: Duplicate

 MR Jobs execution failed.
 -

 Key: HIVE-4633
 URL: https://issues.apache.org/jira/browse/HIVE-4633
 Project: Hive
  Issue Type: Bug
  Components: Query Processor
Affects Versions: 0.11.0
 Environment: Hive-0.11.0 + Hadoop-0.23 
Reporter: rohithsharma
Priority: Critical

 I am running Hive-0.11.0 + Hadoop-0.23 version. All queries that spawn MR 
 jobs got failed. When I look into logs, below exception is thrown in hive.log
 {noformat}
 Caused by: org.apache.hadoop.hive.ql.metadata.HiveException: 
 org.apache.hadoop.hive.ql.metadata.HiveException: Configuration and input 
 path are inconsistent
   at 
 org.apache.hadoop.hive.ql.exec.MapOperator.setChildren(MapOperator.java:522)
   at 
 org.apache.hadoop.hive.ql.exec.ExecMapper.configure(ExecMapper.java:90)
 {noformat}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HIVE-4633) MR Jobs execution failed.


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

rohithsharma commented on HIVE-4633:


Is this fix is from hadoop? The current patch in hive makes continue . I feel 
handling in hadoop is better.

 MR Jobs execution failed.
 -

 Key: HIVE-4633
 URL: https://issues.apache.org/jira/browse/HIVE-4633
 Project: Hive
  Issue Type: Bug
  Components: Query Processor
Affects Versions: 0.11.0
 Environment: Hive-0.11.0 + Hadoop-0.23 
Reporter: rohithsharma
Priority: Critical

 I am running Hive-0.11.0 + Hadoop-0.23 version. All queries that spawn MR 
 jobs got failed. When I look into logs, below exception is thrown in hive.log
 {noformat}
 Caused by: org.apache.hadoop.hive.ql.metadata.HiveException: 
 org.apache.hadoop.hive.ql.metadata.HiveException: Configuration and input 
 path are inconsistent
   at 
 org.apache.hadoop.hive.ql.exec.MapOperator.setChildren(MapOperator.java:522)
   at 
 org.apache.hadoop.hive.ql.exec.ExecMapper.configure(ExecMapper.java:90)
 {noformat}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HIVE-4633) MR Jobs execution failed.


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

rohithsharma commented on HIVE-4633:


Is this fix is from hadoop? The current patch in hive makes continue . I feel 
handling in hadoop is better.

 MR Jobs execution failed.
 -

 Key: HIVE-4633
 URL: https://issues.apache.org/jira/browse/HIVE-4633
 Project: Hive
  Issue Type: Bug
  Components: Query Processor
Affects Versions: 0.11.0
 Environment: Hive-0.11.0 + Hadoop-0.23 
Reporter: rohithsharma
Priority: Critical

 I am running Hive-0.11.0 + Hadoop-0.23 version. All queries that spawn MR 
 jobs got failed. When I look into logs, below exception is thrown in hive.log
 {noformat}
 Caused by: org.apache.hadoop.hive.ql.metadata.HiveException: 
 org.apache.hadoop.hive.ql.metadata.HiveException: Configuration and input 
 path are inconsistent
   at 
 org.apache.hadoop.hive.ql.exec.MapOperator.setChildren(MapOperator.java:522)
   at 
 org.apache.hadoop.hive.ql.exec.ExecMapper.configure(ExecMapper.java:90)
 {noformat}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (HIVE-3644) Connection String for ZK need to be constructed for more than one server.

2012-10-30 Thread rohithsharma (JIRA)

rohithsharma created HIVE-3644:
--

 Summary: Connection String for ZK need to be constructed for more 
than one server.
 Key: HIVE-3644
 URL: https://issues.apache.org/jira/browse/HIVE-3644
 Project: Hive
  Issue Type: Bug
  Components: Locking
Affects Versions: 0.10.0
 Environment: Hadoop-2.0 + Hive-Trunk
Reporter: rohithsharma


Curretnly, connection string constructed for zookeeper is forced to configure 
one zk server for the property hive.zookeeper.quorum.

It should able to create zookeeper connection string for more than one zk 
servers.
ex : hive.zookeeper.quorum=host1,host2,host3
connectionString should be : host1:port,host2:port,host3:port

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HIVE-3644) Connection String for ZK need to be constructed for more than one server.

2012-10-30 Thread rohithsharma (JIRA)


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

rohithsharma commented on HIVE-3644:


I will give patch for this defect.

 Connection String for ZK need to be constructed for more than one server.
 -

 Key: HIVE-3644
 URL: https://issues.apache.org/jira/browse/HIVE-3644
 Project: Hive
  Issue Type: Bug
  Components: Locking
Affects Versions: 0.10.0
 Environment: Hadoop-2.0 + Hive-Trunk
Reporter: rohithsharma

 Curretnly, connection string constructed for zookeeper is forced to configure 
 one zk server for the property hive.zookeeper.quorum.
 It should able to create zookeeper connection string for more than one zk 
 servers.
 ex : hive.zookeeper.quorum=host1,host2,host3
 connectionString should be : host1:port,host2:port,host3:port

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (HIVE-3644) Connection String for ZK need to be constructed for more than one server.

2012-10-30 Thread rohithsharma (JIRA)


 [ 
https://issues.apache.org/jira/browse/HIVE-3644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

rohithsharma updated HIVE-3644:
---

Attachment: HIVE-3644.1.patch

I have attached patch. Please review the patch.

 Connection String for ZK need to be constructed for more than one server.
 -

 Key: HIVE-3644
 URL: https://issues.apache.org/jira/browse/HIVE-3644
 Project: Hive
  Issue Type: Bug
  Components: Locking
Affects Versions: 0.10.0
 Environment: Hadoop-2.0 + Hive-Trunk
Reporter: rohithsharma
 Attachments: HIVE-3644.1.patch


 Curretnly, connection string constructed for zookeeper is forced to configure 
 one zk server for the property hive.zookeeper.quorum.
 It should able to create zookeeper connection string for more than one zk 
 servers.
 ex : hive.zookeeper.quorum=host1,host2,host3
 connectionString should be : host1:port,host2:port,host3:port

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (HIVE-2265) insert overwrite directory for Multilevel directory fails.

2012-09-25 Thread rohithsharma (JIRA)


 [ 
https://issues.apache.org/jira/browse/HIVE-2265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

rohithsharma resolved HIVE-2265.


Resolution: Duplicate

 insert overwrite directory for Multilevel directory fails.
 

 Key: HIVE-2265
 URL: https://issues.apache.org/jira/browse/HIVE-2265
 Project: Hive
  Issue Type: Bug
  Components: Query Processor
Affects Versions: 0.7.0, 0.7.1
 Environment: SuSE-Linux-11
Reporter: rohithsharma

 Couldnot able to complete query execution for insert overwrite directory 
 query when the Directory path is Multilevel.
 create table test ( a int , b int);
 load data local inpath '/home/test.txt' into table test;
 insert overwrite directory '/test' select * f rom test;(This querjy execute 
 successfully)
 insert overwrite directory '/test/test/test' select * f rom test;(This query 
 is throwing below exception)
 {noformat}
 2011-06-27 12:00:15,383 ERROR exec.MoveTask 
 (SessionState.java:printError(343)) - Failed with exception Unable to rename: 
 hdfs://10.18.40.99:9000/tmp/hive-root/hive_2011-06-27_11-59-52_522_5805414771967651042/-ext-1
  to: /test/test/test org.apache.hadoop.hive.ql.metadata.HiveException: Unable 
 to rename: 
 hdfs://10.18.40.99:9000/tmp/hive-root/hive_2011-06-27_11-59-52_522_5805414771967651042/-ext-1
  to: /test/test/test at 
 org.apache.hadoop.hive.ql.exec.MoveTask.moveFile(MoveTask.java:78)
   at org.apache.hadoop.hive.ql.exec.MoveTask.execute(MoveTask.java:122)
   at org.apache.hadoop.hive.ql.exec.Task.executeTask(Task.java:130)
   at 
 org.apache.hadoop.hive.ql.exec.TaskRunner.runSequential(TaskRunner.java:57)
   at org.apache.hadoop.hive.ql.Driver.launchTask(Driver.java:1063)
   at org.apache.hadoop.hive.ql.Driver.execute(Driver.java:900)
   at org.apache.hadoop.hive.ql.Driver.run(Driver.java:748)
   at 
 org.apache.hadoop.hive.service.HiveServer$HiveServerHandler.execute(HiveServer.java:116)
   at 
 org.apache.hadoop.hive.service.ThriftHive$Processor$execute.process(ThriftHive.java:699)
   at 
 org.apache.hadoop.hive.service.ThriftHive$Processor.process(ThriftHive.java:677)
   at 
 org.apache.thrift.server.TThreadPoolServer$WorkerProcess.run(TThreadPoolServer.java:253)
   at 
 java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
   at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
   at java.lang.Thread.run(Thread.java:619)
 2011-06-27 12:00:15,384 ERROR ql.Driver (SessionState.java:printError(343)) - 
 FAILED: Execution Error, return code 1 from 
 org.apache.hadoop.hive.ql.exec.MoveTask
 {noformat}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HIVE-2265) insert overwrite directory for Multilevel directory fails.

2012-09-25 Thread rohithsharma (JIRA)


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

rohithsharma commented on HIVE-2265:


This issue is resolved. Making duplicate of Hive-1975.

 insert overwrite directory for Multilevel directory fails.
 

 Key: HIVE-2265
 URL: https://issues.apache.org/jira/browse/HIVE-2265
 Project: Hive
  Issue Type: Bug
  Components: Query Processor
Affects Versions: 0.7.0, 0.7.1
 Environment: SuSE-Linux-11
Reporter: rohithsharma

 Couldnot able to complete query execution for insert overwrite directory 
 query when the Directory path is Multilevel.
 create table test ( a int , b int);
 load data local inpath '/home/test.txt' into table test;
 insert overwrite directory '/test' select * f rom test;(This querjy execute 
 successfully)
 insert overwrite directory '/test/test/test' select * f rom test;(This query 
 is throwing below exception)
 {noformat}
 2011-06-27 12:00:15,383 ERROR exec.MoveTask 
 (SessionState.java:printError(343)) - Failed with exception Unable to rename: 
 hdfs://10.18.40.99:9000/tmp/hive-root/hive_2011-06-27_11-59-52_522_5805414771967651042/-ext-1
  to: /test/test/test org.apache.hadoop.hive.ql.metadata.HiveException: Unable 
 to rename: 
 hdfs://10.18.40.99:9000/tmp/hive-root/hive_2011-06-27_11-59-52_522_5805414771967651042/-ext-1
  to: /test/test/test at 
 org.apache.hadoop.hive.ql.exec.MoveTask.moveFile(MoveTask.java:78)
   at org.apache.hadoop.hive.ql.exec.MoveTask.execute(MoveTask.java:122)
   at org.apache.hadoop.hive.ql.exec.Task.executeTask(Task.java:130)
   at 
 org.apache.hadoop.hive.ql.exec.TaskRunner.runSequential(TaskRunner.java:57)
   at org.apache.hadoop.hive.ql.Driver.launchTask(Driver.java:1063)
   at org.apache.hadoop.hive.ql.Driver.execute(Driver.java:900)
   at org.apache.hadoop.hive.ql.Driver.run(Driver.java:748)
   at 
 org.apache.hadoop.hive.service.HiveServer$HiveServerHandler.execute(HiveServer.java:116)
   at 
 org.apache.hadoop.hive.service.ThriftHive$Processor$execute.process(ThriftHive.java:699)
   at 
 org.apache.hadoop.hive.service.ThriftHive$Processor.process(ThriftHive.java:677)
   at 
 org.apache.thrift.server.TThreadPoolServer$WorkerProcess.run(TThreadPoolServer.java:253)
   at 
 java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
   at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
   at java.lang.Thread.run(Thread.java:619)
 2011-06-27 12:00:15,384 ERROR ql.Driver (SessionState.java:printError(343)) - 
 FAILED: Execution Error, return code 1 from 
 org.apache.hadoop.hive.ql.exec.MoveTask
 {noformat}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HIVE-2084) Upgrade datanucleus from 2.0.3 to 3.0.1

2012-09-24 Thread rohithsharma (JIRA)


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

rohithsharma commented on HIVE-2084:


Could anyone please update on this issue.? 

 Upgrade datanucleus from 2.0.3 to 3.0.1
 ---

 Key: HIVE-2084
 URL: https://issues.apache.org/jira/browse/HIVE-2084
 Project: Hive
  Issue Type: Improvement
  Components: Metastore
Reporter: Ning Zhang
Assignee: Sushanth Sowmyan
  Labels: datanucleus
 Attachments: ASF.LICENSE.NOT.GRANTED--HIVE-2084.D2397.1.patch, 
 HIVE-2084.1.patch.txt, HIVE-2084.2.patch.txt, HIVE-2084.patch


 It seems the datanucleus 2.2.3 does a better join in caching. The time it 
 takes to get the same set of partition objects takes about 1/4 of the time it 
 took for the first time. While with 2.0.3, it took almost the same amount of 
 time in the second execution. We should retest the test case mentioned in 
 HIVE-1853, HIVE-1862.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HIVE-3469) When new hive cluster is started, hive jdbc client hangs.

2012-09-23 Thread rohithsharma (JIRA)


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

rohithsharma commented on HIVE-3469:


Applying patch of HIVE-2937 has fixed all 3 issue as per description. This we 
can mark as duplicate of 2937.

 When new hive cluster is started, hive jdbc client hangs.
 -

 Key: HIVE-3469
 URL: https://issues.apache.org/jira/browse/HIVE-3469
 Project: Hive
  Issue Type: Bug
  Components: Clients, Metastore, Thrift API
 Environment: Hadoop-2.0.1 + Hive-0.9.0
Reporter: rohithsharma

 The scenario is as follows  : 
 For the new hive cluster , when multiple hive client is getting the 
 connection for hive server , there are 3 problems in metastore , hive client.
 1. Since the derby is booted at first connection,  multiple client try to 
 create database.One of the client succeed and another one throw exception 
 because of *unique primary constraint* in metatables.
 2. Once the Runtime exception is throw, the hive client which is made 
 connection request will hang forever.
 3. Potentially ConcurrentModificationException is thrown by JDOQuery.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HIVE-3469) When new hive cluster is started, hive jdbc client hangs.

2012-09-17 Thread rohithsharma (JIRA)

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

rohithsharma commented on HIVE-3469:

bq. Any idea why this doesn't solve the problem?
I am using hive branch-0.9.0. The above problem is fixed in Hive-Trunk only.

I gone through the hive-trunk code for the above problem. I have one doubt on
the synchronization,
Exact synchronization problem exist on method createDefaultDB_core(). Why it is
synchronized for calling method createDefaultDB().?

Correct me If I am wrong, synchronizing calling method impact would be on
getting client connection is delayed. There is if block in method
createDefaultDB() that check for flag createDefaultDB. Synchronizing to
this method lead execute this if check only one client. This if check we can do
parallel by bringing down synchronization one layer to the method
createDefaultDB_core().

When new hive cluster is started, hive jdbc client hangs.
-

Key: HIVE-3469
URL: https://issues.apache.org/jira/browse/HIVE-3469
Project: Hive
Issue Type: Bug
Components: Clients, Metastore, Thrift API
Environment: Hadoop-2.0.1 + Hive-0.9.0
Reporter: rohithsharma

The scenario is as follows :
For the new hive cluster , when multiple hive client is getting the
connection for hive server , there are 3 problems in metastore , hive client.
1. Since the derby is booted at first connection, multiple client try to
create database.One of the client succeed and another one throw exception
because of *unique primary constraint* in metatables.
2. Once the Runtime exception is throw, the hive client which is made
connection request will hang forever.
3. Potentially ConcurrentModificationException is thrown by JDOQuery.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (HIVE-3469) When new hive cluster is started, hive jdbc client hangs.

2012-09-15 Thread rohithsharma (JIRA)

rohithsharma created HIVE-3469:
--

 Summary: When new hive cluster is started, hive jdbc client hangs.
 Key: HIVE-3469
 URL: https://issues.apache.org/jira/browse/HIVE-3469
 Project: Hive
  Issue Type: Bug
  Components: Clients, Metastore, Thrift API
 Environment: Hadoop-2.0.1 + Hive-0.9.0
Reporter: rohithsharma


The scenario is as follows  : 
For the new hive cluster , when multiple hive client is getting the connection 
for hive server , there are 3 problems in metastore , hive client.
1. Since the derby is booted at first connection,  multiple client try to 
create database.One of the client succeed and another one throw exception 
because of *unique primary constraint* in metatables.

2. Once the Runtime exception is throw, the hive client which is made 
connection request will hang forever.

3. Potentially ConcurrentModificationException is thrown by JDOQuery.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HIVE-3469) When new hive cluster is started, hive jdbc client hangs.

2012-09-15 Thread rohithsharma (JIRA)


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

rohithsharma commented on HIVE-3469:


1. For the first problem , exception from JDO is primary constraint.

bq. Caused by: javax.jdo.JDODataStoreException: Insert of object 
org.apache.hadoop.hive.metastore.model.MDatabase@63280c85 using statement 
INSERT INTO DBS (DB_ID,DB_LOCATION_URI,NAME,DESC) VALUES (?,?,?,?) failed 
: The statement was aborted because it would have caused a duplicate key value 
in a unique or primary key constraint or unique index identified by 
'UNIQUE_DATABASE' defined on 'DBS'.

2. For the third proble, exception trace is  
{noformat}
2012-09-14 20:26:22,507 ERROR server.TThreadPoolServer 
(TThreadPoolServer.java:run(182)) - Error occurred during processing of message.
java.lang.RuntimeException: java.util.ConcurrentModificationException
at 
org.apache.hadoop.hive.service.HiveServer$ThriftHiveProcessorFactory.getProcessor(HiveServer.java:572)
at 
org.apache.thrift.server.TThreadPoolServer$WorkerProcess.run(TThreadPoolServer.java:169)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
Caused by: java.util.ConcurrentModificationException
at java.util.Hashtable$Enumerator.next(Hashtable.java:1031)
at 
org.datanucleus.store.rdbms.query.legacy.JDOQLQuery.getParsedImports(JDOQLQuery.java:364)
at 
org.datanucleus.store.rdbms.query.legacy.JDOQLQuery.compileInternal(JDOQLQuery.java:174)
at org.datanucleus.store.query.Query.executeQuery(Query.java:1628)
at 
org.datanucleus.store.rdbms.query.legacy.JDOQLQuery.executeQuery(JDOQLQuery.java:245)
at org.datanucleus.store.query.Query.executeWithArray(Query.java:1499)
at org.datanucleus.jdo.JDOQuery.execute(JDOQuery.java:243)
at 
org.apache.hadoop.hive.metastore.ObjectStore.getMDatabase(ObjectStore.java:389)
at 
org.apache.hadoop.hive.metastore.ObjectStore.getDatabase(ObjectStore.java:408)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 ...
 ...
 at $Proxy0.getDatabase(Unknown Source)
at 
org.apache.hadoop.hive.metastore.HiveMetaStore$HMSHandler.createDefaultDB_core(HiveMetaStore.java:351)
at 
org.apache.hadoop.hive.metastore.HiveMetaStore$HMSHandler.createDefaultDB(HiveMetaStore.java:375)
at 
org.apache.hadoop.hive.metastore.HiveMetaStore$HMSHandler.init(HiveMetaStore.java:278)
  
{noformat}

 When new hive cluster is started, hive jdbc client hangs.
 -

 Key: HIVE-3469
 URL: https://issues.apache.org/jira/browse/HIVE-3469
 Project: Hive
  Issue Type: Bug
  Components: Clients, Metastore, Thrift API
 Environment: Hadoop-2.0.1 + Hive-0.9.0
Reporter: rohithsharma

 The scenario is as follows  : 
 For the new hive cluster , when multiple hive client is getting the 
 connection for hive server , there are 3 problems in metastore , hive client.
 1. Since the derby is booted at first connection,  multiple client try to 
 create database.One of the client succeed and another one throw exception 
 because of *unique primary constraint* in metatables.
 2. Once the Runtime exception is throw, the hive client which is made 
 connection request will hang forever.
 3. Potentially ConcurrentModificationException is thrown by JDOQuery.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HIVE-3469) When new hive cluster is started, hive jdbc client hangs.

2012-09-15 Thread rohithsharma (JIRA)


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

rohithsharma commented on HIVE-3469:


Any exception in above 1 or 3, Hive client hangs forever.

If we synchronize Metastore.createDefaultDB_core(), all the 3 problem can be 
resolved. Please suggest your opinion..

 When new hive cluster is started, hive jdbc client hangs.
 -

 Key: HIVE-3469
 URL: https://issues.apache.org/jira/browse/HIVE-3469
 Project: Hive
  Issue Type: Bug
  Components: Clients, Metastore, Thrift API
 Environment: Hadoop-2.0.1 + Hive-0.9.0
Reporter: rohithsharma

 The scenario is as follows  : 
 For the new hive cluster , when multiple hive client is getting the 
 connection for hive server , there are 3 problems in metastore , hive client.
 1. Since the derby is booted at first connection,  multiple client try to 
 create database.One of the client succeed and another one throw exception 
 because of *unique primary constraint* in metatables.
 2. Once the Runtime exception is throw, the hive client which is made 
 connection request will hang forever.
 3. Potentially ConcurrentModificationException is thrown by JDOQuery.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (HIVE-3425) NPE exception in Tests escape1 and escape2.

2012-09-03 Thread rohithsharma (JIRA)

rohithsharma created HIVE-3425:
--

 Summary: NPE exception in Tests escape1 and escape2.
 Key: HIVE-3425
 URL: https://issues.apache.org/jira/browse/HIVE-3425
 Project: Hive
  Issue Type: Bug
  Components: Metastore, Tests
Affects Versions: 0.10.0, 0.9.1
 Environment: Hive-0.9.1 + 
Postgres as metastore.
Reporter: rohithsharma


Tests are executed with Postgres as metastore. These 2 test
testCliDriver_escape1 and 
testCliDriver_escape2 fails throwing NPE.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HIVE-3425) NPE exception in Tests escape1 and escape2.

2012-09-03 Thread rohithsharma (JIRA)


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

rohithsharma commented on HIVE-3425:


Exception trace is as follows

{noformat}
2012-09-03 15:11:15,903 ERROR exec.Task (SessionState.java:printError(400)) - 
Failed with exception java.lang.NullPointerException
org.apache.hadoop.hive.ql.metadata.HiveException: java.lang.NullPointerException
at org.apache.hadoop.hive.ql.metadata.Hive.getPartition(Hive.java:1460)
at org.apache.hadoop.hive.ql.metadata.Hive.loadPartition(Hive.java:1158)
at 
org.apache.hadoop.hive.ql.metadata.Hive.loadDynamicPartitions(Hive.java:1232)
at org.apache.hadoop.hive.ql.exec.MoveTask.execute(MoveTask.java:269)
at org.apache.hadoop.hive.ql.exec.Task.executeTask(Task.java:135)
at 
org.apache.hadoop.hive.ql.exec.TaskRunner.runSequential(TaskRunner.java:57)
at org.apache.hadoop.hive.ql.Driver.launchTask(Driver.java:1329)
at org.apache.hadoop.hive.ql.Driver.execute(Driver.java:1121)
at org.apache.hadoop.hive.ql.Driver.run(Driver.java:954)
at 
org.apache.hadoop.hive.cli.CliDriver.processLocalCmd(CliDriver.java:258)
at org.apache.hadoop.hive.cli.CliDriver.processCmd(CliDriver.java:215)
at org.apache.hadoop.hive.cli.CliDriver.processLine(CliDriver.java:406)
at org.apache.hadoop.hive.cli.CliDriver.run(CliDriver.java:689)
at org.apache.hadoop.hive.cli.CliDriver.main(CliDriver.java:557)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.hadoop.util.RunJar.main(RunJar.java:208)
Caused by: java.lang.NullPointerException
at 
org.datanucleus.store.AbstractStoreManager.getConnection(AbstractStoreManager.java:301)
at 
org.datanucleus.store.rdbms.scostore.RDBMSMapEntrySetStore.size(RDBMSMapEntrySetStore.java:126)
at org.datanucleus.sco.backed.Map.size(Map.java:532)
at 
org.datanucleus.store.mapped.mapping.MapMapping.postInsert(MapMapping.java:131)
at 
org.datanucleus.store.rdbms.request.InsertRequest.execute(InsertRequest.java:515)
at 
org.datanucleus.store.rdbms.RDBMSPersistenceHandler.insertTable(RDBMSPersistenceHandler.java:146)
at 
org.datanucleus.store.rdbms.RDBMSPersistenceHandler.insertObject(RDBMSPersistenceHandler.java:121)
at 
org.datanucleus.jdo.state.JDOStateManagerImpl.internalMakePersistent(JDOStateManagerImpl.java:3275)
at 
org.datanucleus.jdo.state.JDOStateManagerImpl.makePersistent(JDOStateManagerImpl.java:3249)
at 
org.datanucleus.ObjectManagerImpl.persistObjectInternal(ObjectManagerImpl.java:1428)
at 
org.datanucleus.store.mapped.mapping.PersistableMapping.setObjectAsValue(PersistableMapping.java:664)
at 
org.datanucleus.store.mapped.mapping.PersistableMapping.setObject(PersistableMapping.java:423)
at 
org.datanucleus.store.rdbms.fieldmanager.ParameterSetter.storeObjectField(ParameterSetter.java:197)
at 
org.datanucleus.state.AbstractStateManager.providedObjectField(AbstractStateManager.java:1023)
at 
org.apache.hadoop.hive.metastore.model.MPartition.jdoProvideField(MPartition.java)
at 
org.apache.hadoop.hive.metastore.model.MPartition.jdoProvideFields(MPartition.java)
at 
org.datanucleus.jdo.state.JDOStateManagerImpl.provideFields(JDOStateManagerImpl.java:2803)
at 
org.datanucleus.store.rdbms.request.InsertRequest.execute(InsertRequest.java:294)
at 
org.datanucleus.store.rdbms.RDBMSPersistenceHandler.insertTable(RDBMSPersistenceHandler.java:146)
at 
org.datanucleus.store.rdbms.RDBMSPersistenceHandler.insertObject(RDBMSPersistenceHandler.java:121)
at 
org.datanucleus.jdo.state.JDOStateManagerImpl.internalMakePersistent(JDOStateManagerImpl.java:3275)
at 
org.datanucleus.jdo.state.JDOStateManagerImpl.makePersistent(JDOStateManagerImpl.java:3249)
at 
org.datanucleus.ObjectManagerImpl.persistObjectInternal(ObjectManagerImpl.java:1428)
at 
org.datanucleus.ObjectManagerImpl.persistObject(ObjectManagerImpl.java:1236)
at 
org.datanucleus.jdo.JDOPersistenceManager.jdoMakePersistent(JDOPersistenceManager.java:655)
at 
org.datanucleus.jdo.JDOPersistenceManager.makePersistent(JDOPersistenceManager.java:680)
at 
org.apache.hadoop.hive.metastore.ObjectStore.addPartition(ObjectStore.java:1056)
at sun.reflect.GeneratedMethodAccessor51.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at

[jira] [Created] (HIVE-3419) drop partition does not work for non-equality oprator.

2012-08-31 Thread rohithsharma (JIRA)

rohithsharma created HIVE-3419:
--

 Summary: drop partition does not work for non-equality oprator.
 Key: HIVE-3419
 URL: https://issues.apache.org/jira/browse/HIVE-3419
 Project: Hive
  Issue Type: Bug
  Components: Metastore, Query Processor
Affects Versions: 0.10.0, 0.9.1
 Environment: Hive -0.9.1
postgres-9.0.7 as metastore.
Reporter: rohithsharma


Drop partition query failes when below query is executed with postgres as 
metastore.Whereas when derby is used, drop partition query is pased.

create table ptestfilter (a string, b int) partitioned by (c string);
alter table ptestfilter1 add partition (c='1');
alter table ptestfilter1 add partition (c='2');
alter table ptestfilter1 drop partition (c!='2');-- failed


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HIVE-3419) drop partition does not work for non-equality oprator.

2012-08-31 Thread rohithsharma (JIRA)


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

rohithsharma commented on HIVE-3419:


JDO throws NullPointerException for above partitions.

{noformat}
2012-08-31 12:13:26,466 DEBUG metastore.ObjectStore 
(ObjectStore.java:listMPartitionsByFilter(1680)) - Executing 
listMPartitionsByFilter
2012-08-31 12:13:26,474 DEBUG metastore.ObjectStore 
(ObjectStore.java:makeQueryFilterString(1636)) - jdoFilter =  
partitionName.substring(partitionName.indexOf(c=)+2) != hive_filter_param_0
2012-08-31 12:13:26,475 DEBUG metastore.ObjectStore 
(ObjectStore.java:listMPartitionsByFilter(1701)) - Filter specified is c  
'2', JDOQL filter is table.tableName == t1  table.database.name == t2  ( 
partitionName.substring(partitionName.indexOf(c=)+2) != hive_filter_param_0 )
2012-08-31 12:13:26,478 ERROR ql.Driver (SessionState.java:printError(400)) - 
FAILED: Error in semantic analysis: Partition not found c  '2'
org.apache.hadoop.hive.ql.parse.SemanticException: Partition not found c  '2'
at 
org.apache.hadoop.hive.ql.parse.DDLSemanticAnalyzer.addTableDropPartsOutputs(DDLSemanticAnalyzer.java:2249)
at 
org.apache.hadoop.hive.ql.parse.DDLSemanticAnalyzer.analyzeAlterTableDropParts(DDLSemanticAnalyzer.java:1818)
at 
org.apache.hadoop.hive.ql.parse.DDLSemanticAnalyzer.analyzeInternal(DDLSemanticAnalyzer.java:300)
at 
org.apache.hadoop.hive.ql.parse.BaseSemanticAnalyzer.analyze(BaseSemanticAnalyzer.java:244)
...
...
...
Caused by: java.lang.NullPointerException
at 
org.datanucleus.store.mapped.mapping.MappingHelper.getMappingIndices(MappingHelper.java:35)
at 
org.datanucleus.store.mapped.expression.StatementText.applyParametersToStatement(StatementText.java:194)
at 
org.datanucleus.store.rdbms.query.RDBMSQueryUtils.getPreparedStatementForQuery(RDBMSQueryUtils.java:233)
at 
org.datanucleus.store.rdbms.query.legacy.SQLEvaluator.evaluate(SQLEvaluator.java:115)
at 
org.datanucleus.store.rdbms.query.legacy.JDOQLQuery.performExecute(JDOQLQuery.java:288)
at org.datanucleus.store.query.Query.executeQuery(Query.java:1657)
at 
org.datanucleus.store.rdbms.query.legacy.JDOQLQuery.executeQuery(JDOQLQuery.java:245)
at org.datanucleus.store.query.Query.executeWithMap(Query.java:1526)
at org.datanucleus.jdo.JDOQuery.executeWithMap(JDOQuery.java:334)
at 
org.apache.hadoop.hive.metastore.ObjectStore.listMPartitionsByFilter(ObjectStore.java:1711)
at 
org.apache.hadoop.hive.metastore.ObjectStore.getPartitionsByFilter(ObjectStore.java:1586)
{noformat}

 drop partition does not work for non-equality oprator.
 --

 Key: HIVE-3419
 URL: https://issues.apache.org/jira/browse/HIVE-3419
 Project: Hive
  Issue Type: Bug
  Components: Metastore, Query Processor
Affects Versions: 0.10.0, 0.9.1
 Environment: Hive -0.9.1
 postgres-9.0.7 as metastore.
Reporter: rohithsharma

 Drop partition query failes when below query is executed with postgres as 
 metastore.Whereas when derby is used, drop partition query is pased.
 create table ptestfilter (a string, b int) partitioned by (c string);
 alter table ptestfilter1 add partition (c='1');
 alter table ptestfilter1 add partition (c='2');
 alter table ptestfilter1 drop partition (c!='2');-- failed

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HIVE-3419) drop partition does not work for non-equality oprator.

2012-08-31 Thread rohithsharma (JIRA)


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

rohithsharma commented on HIVE-3419:


I think it looks like problem with datanuclues.I found another issue HIVE-2609 
with same cause for the problem.

 drop partition does not work for non-equality oprator.
 --

 Key: HIVE-3419
 URL: https://issues.apache.org/jira/browse/HIVE-3419
 Project: Hive
  Issue Type: Bug
  Components: Metastore, Query Processor
Affects Versions: 0.10.0, 0.9.1
 Environment: Hive -0.9.1
 postgres-9.0.7 as metastore.
Reporter: rohithsharma

 Drop partition query failes when below query is executed with postgres as 
 metastore.Whereas when derby is used, drop partition query is pased.
 create table ptestfilter (a string, b int) partitioned by (c string);
 alter table ptestfilter1 add partition (c='1');
 alter table ptestfilter1 add partition (c='2');
 alter table ptestfilter1 drop partition (c!='2');-- failed

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (HIVE-3309) drop partition doesnot work for mixture of string and non-string columns for non-equality operatior

2012-08-08 Thread rohithsharma (JIRA)


 [ 
https://issues.apache.org/jira/browse/HIVE-3309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

rohithsharma updated HIVE-3309:
---

Status: Patch Available  (was: Open)

 drop partition doesnot work for mixture of string and non-string columns for 
 non-equality operatior
 ---

 Key: HIVE-3309
 URL: https://issues.apache.org/jira/browse/HIVE-3309
 Project: Hive
  Issue Type: Bug
  Components: Metastore, Query Processor
Affects Versions: 0.10.0, 0.9.1
 Environment: SuSE 11 SP 1
 Hadoop Cluster + Hive
Reporter: rohithsharma
Priority: Minor
  Labels: patch
 Fix For: 0.10.0

 Attachments: HIVE-3309.patch, HIVE-3309.patch


 There is still problem in drop partition columns if the partition columns 
 are mixture of string and non-string.
 There is behavioural change after fixing HIVE-3063.
 Before fix
 ==
 create table ptestfilter (a string, b int) partitioned by (c string, d int);
 alter table ptestfilter add partition (c='1', d=2);
 alter table ptestFilter add partition (c='2', d=1);
 alter table ptestfilter drop partition (c'2'); //this will execute fine
 After fix
 ==
 create table ptestfilter (a string, b int) partitioned by (c string, d int);
 alter table ptestfilter add partition (c='1', d=2);
 alter table ptestFilter add partition (c='2', d=1);
 alter table ptestfilter drop partition (c'2'); //this will fail to execute.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HIVE-2532) Evaluation of non-deterministic/stateful UDFs should not be skipped even if constant oi is returned.

2012-08-02 Thread rohithsharma (JIRA)


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

rohithsharma commented on HIVE-2532:


Hi,
I have one doubt on ASSERT_TRUE() funtion. Currently ASSERT_TRUE() is returning 
NULL.Its PrimitiveType is VOID.Once query is executed in CLI mode, output of 
query prints NULL in console where as in JDBC client throw an 
exception(HIVE-3200).The serde implimentation for PrimitiveType VOID throw 
exception.

Correct me if I am wrong,
From the user perspective I feel its better to return boolean value i.e TRUE 
instead of returning NULL. Please give your opinion..


 Evaluation of non-deterministic/stateful UDFs should not be skipped even if 
 constant oi is returned.
 

 Key: HIVE-2532
 URL: https://issues.apache.org/jira/browse/HIVE-2532
 Project: Hive
  Issue Type: Bug
Reporter: Jonathan Chang
Assignee: Jonathan Chang
 Fix For: 0.8.0

 Attachments: D273.1.patch, D273.2.patch, D273.3.patch, D273.4.patch, 
 D273.4.patch, D273.4.patch


 Even if constant oi is returned, these may have stateful/side-effect behavior 
 and hence need to be called each cycle.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HIVE-2532) Evaluation of non-deterministic/stateful UDFs should not be skipped even if constant oi is returned.

2012-08-02 Thread rohithsharma (JIRA)


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

rohithsharma commented on HIVE-2532:


I tested with changing implementation to boolean.All the positive scenario 
works fine. Whereas , SELECT 1 + assert_true FROM src  fails.

{noformat}
2012-08-02 16:34:31,173 ERROR ql.Driver (SessionState.java:printError(400)) - 
FAILED: Error in semantic analysis: Line 1:7 Wrong arguments '0': Unable to 
find a common class betweentypes int and boolean
org.apache.hadoop.hive.ql.parse.SemanticException: Line 1:7 Wrong arguments 
'0': Unable to find a common class betweentypes int and boolean
at 
org.apache.hadoop.hive.ql.parse.TypeCheckProcFactory$DefaultExprProcessor.process(TypeCheckProcFactory.java:896)
at 
org.apache.hadoop.hive.ql.lib.DefaultRuleDispatcher.dispatch(DefaultRuleDispatcher.java:89)
{noformat}

With string return type, SELECT 1 + assert_true FROM src query execution is 
successfull.

 Evaluation of non-deterministic/stateful UDFs should not be skipped even if 
 constant oi is returned.
 

 Key: HIVE-2532
 URL: https://issues.apache.org/jira/browse/HIVE-2532
 Project: Hive
  Issue Type: Bug
Reporter: Jonathan Chang
Assignee: Jonathan Chang
 Fix For: 0.8.0

 Attachments: D273.1.patch, D273.2.patch, D273.3.patch, D273.4.patch, 
 D273.4.patch, D273.4.patch


 Even if constant oi is returned, these may have stateful/side-effect behavior 
 and hence need to be called each cycle.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HIVE-3324) analyze command is not gathering num_rows present in the table.

2012-08-01 Thread rohithsharma (JIRA)


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

rohithsharma commented on HIVE-3324:


There are 2 problems for analyze command.

1. JDBCStastPublisher fails to connect to database since derby jar is not in 
classpath.In YarnChild logs we get below exception.
{noformat}
2012-08-01 10:25:17,954 ERROR [main] 
org.apache.hadoop.hive.ql.stats.jdbc.JDBCStatsPublisher: Error during 
instantiating JDBC driver org.apache.derby.jdbc.EmbeddedDriver. 
java.lang.ClassNotFoundException: org.apache.derby.jdbc.EmbeddedDriver
at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:169)
at 
org.apache.hadoop.hive.ql.stats.jdbc.JDBCStatsPublisher.connect(JDBCStatsPublisher.java:69)
at 
org.apache.hadoop.hive.ql.exec.TableScanOperator.publishStats(TableScanOperator.java:236)
{noformat}

 Above problem can be resolved by setting hive.aux.jars.path for derby jar.

2. JVM of Hive and YarnChild are different.So dbconnectionstring should be 
common location.If it is set to common location , then there is problme if the 
NodeManager and Hive are running in differetn machine.

 analyze command is not gathering num_rows present in the table.
 -

 Key: HIVE-3324
 URL: https://issues.apache.org/jira/browse/HIVE-3324
 Project: Hive
  Issue Type: Bug
  Components: Statistics
Affects Versions: 0.10.0, 0.9.1
Reporter: rohithsharma

 When analyze command is executed, collectableStats i.e num_rows and 
 raw_data_size is always zero even though table contains data.
 bq. [num_partitions: 0, num_files: 1, num_rows: 0, total_size: 5812, 
 raw_data_size: 0]

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (HIVE-3324) analyze command is not gathering num_rows present in the table.

2012-07-31 Thread rohithsharma (JIRA)

rohithsharma created HIVE-3324:
--

 Summary: analyze command is not gathering num_rows present in 
the table.
 Key: HIVE-3324
 URL: https://issues.apache.org/jira/browse/HIVE-3324
 Project: Hive
  Issue Type: Bug
  Components: Statistics
Affects Versions: 0.10.0, 0.9.1
Reporter: rohithsharma


When analyze command is executed, collectableStats i.e num_rows and 
raw_data_size is always zero even though table contains data.
bq. [num_partitions: 0, num_files: 1, num_rows: 0, total_size: 5812, 
raw_data_size: 0]


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HIVE-3324) analyze command is not gathering num_rows present in the table.

2012-07-31 Thread rohithsharma (JIRA)


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

rohithsharma commented on HIVE-3324:


From the code I see, default configuration is for connecting to database is  
hive.stats.dbconnectionstring=jdbc:derby:;databaseName=TempStatsStore;create=true.When
 analyze command is executed, initialy PARTITION_STATS_V2 is created at HIVE 
JVM whereas statistics publishing is done at YarnChild. While publishing the 
statistics to database, directly executing inserting data into to table.Since 
yarn child is different jvm, it doesnot find initially created table 
PARTITION_STATS_V2.




 analyze command is not gathering num_rows present in the table.
 -

 Key: HIVE-3324
 URL: https://issues.apache.org/jira/browse/HIVE-3324
 Project: Hive
  Issue Type: Bug
  Components: Statistics
Affects Versions: 0.10.0, 0.9.1
Reporter: rohithsharma

 When analyze command is executed, collectableStats i.e num_rows and 
 raw_data_size is always zero even though table contains data.
 bq. [num_partitions: 0, num_files: 1, num_rows: 0, total_size: 5812, 
 raw_data_size: 0]

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HIVE-3324) analyze command is not gathering num_rows present in the table.

2012-07-31 Thread rohithsharma (JIRA)


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

rohithsharma commented on HIVE-3324:


I have one doubt for analyze configuration.
bq.Is databaseName should be absolute path so that 2 JVM's can share this 
database.? 
If yes, its better to document in Information document.

I got correct statistics when database is shared amoung JVM's i.e 
hive.stats.dbconnectionstring=jdbc:derby:;databaseName=/home/TempStatsStore;create=true
 :-)

 analyze command is not gathering num_rows present in the table.
 -

 Key: HIVE-3324
 URL: https://issues.apache.org/jira/browse/HIVE-3324
 Project: Hive
  Issue Type: Bug
  Components: Statistics
Affects Versions: 0.10.0, 0.9.1
Reporter: rohithsharma

 When analyze command is executed, collectableStats i.e num_rows and 
 raw_data_size is always zero even though table contains data.
 bq. [num_partitions: 0, num_files: 1, num_rows: 0, total_size: 5812, 
 raw_data_size: 0]

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HIVE-3309) drop partition doesnot work for mixture of string and non-string columns for non-equality operatior

2012-07-30 Thread rohithsharma (JIRA)


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

rohithsharma commented on HIVE-3309:


If the query contains partition column of type only string , then non-equality 
operator throw exception.
Example : 
1. create table ptestfilter (a string, b int) partitioned by (c string, d int);
2. alter table ptestfilter add partition (c='1', d=1);
3. alter table ptestfilter drop partition (c'2');

In above example, line-3 throws exception. But expected is query should drop 
partition columns which are less then 2.

 drop partition doesnot work for mixture of string and non-string columns for 
 non-equality operatior
 ---

 Key: HIVE-3309
 URL: https://issues.apache.org/jira/browse/HIVE-3309
 Project: Hive
  Issue Type: Bug
  Components: Metastore, Query Processor
Affects Versions: 0.9.1
 Environment: SuSE 11 SP 1
 Hadoop Cluster + Hive
Reporter: rohithsharma
Priority: Minor

 There is still problem in drop partition columns if the partition columns 
 are mixture of string and non-string.
 There is behavioural change after fixing HIVE-3063.
 Before fix
 ==
 create table ptestfilter (a string, b int) partitioned by (c string, d int);
 alter table ptestfilter add partition (c='1', d=2);
 alter table ptestFilter add partition (c='2', d=1);
 alter table ptestfilter drop partition (c'2'); //this will execute fine
 After fix
 ==
 create table ptestfilter (a string, b int) partitioned by (c string, d int);
 alter table ptestfilter add partition (c='1', d=2);
 alter table ptestFilter add partition (c='2', d=1);
 alter table ptestfilter drop partition (c'2'); //this will fail to execute.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (HIVE-3309) drop partition doesnot work for mixture of string and non-string columns for non-equality operatior

2012-07-30 Thread rohithsharma (JIRA)


 [ 
https://issues.apache.org/jira/browse/HIVE-3309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

rohithsharma updated HIVE-3309:
---

Fix Version/s: 0.10.0
   Labels: patch  (was: )
Affects Version/s: 0.10.0
   Status: Patch Available  (was: Open)

I am submitting patch with initial thoughts.Please review the patch.
I will submit actual patch with test if current idea is accepted.

 drop partition doesnot work for mixture of string and non-string columns for 
 non-equality operatior
 ---

 Key: HIVE-3309
 URL: https://issues.apache.org/jira/browse/HIVE-3309
 Project: Hive
  Issue Type: Bug
  Components: Metastore, Query Processor
Affects Versions: 0.10.0, 0.9.1
 Environment: SuSE 11 SP 1
 Hadoop Cluster + Hive
Reporter: rohithsharma
Priority: Minor
  Labels: patch
 Fix For: 0.10.0


 There is still problem in drop partition columns if the partition columns 
 are mixture of string and non-string.
 There is behavioural change after fixing HIVE-3063.
 Before fix
 ==
 create table ptestfilter (a string, b int) partitioned by (c string, d int);
 alter table ptestfilter add partition (c='1', d=2);
 alter table ptestFilter add partition (c='2', d=1);
 alter table ptestfilter drop partition (c'2'); //this will execute fine
 After fix
 ==
 create table ptestfilter (a string, b int) partitioned by (c string, d int);
 alter table ptestfilter add partition (c='1', d=2);
 alter table ptestFilter add partition (c='2', d=1);
 alter table ptestfilter drop partition (c'2'); //this will fail to execute.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (HIVE-3309) drop partition doesnot work for mixture of string and non-string columns for non-equality operatior

2012-07-30 Thread rohithsharma (JIRA)


 [ 
https://issues.apache.org/jira/browse/HIVE-3309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

rohithsharma updated HIVE-3309:
---

Attachment: HIVE-3309.patch

 drop partition doesnot work for mixture of string and non-string columns for 
 non-equality operatior
 ---

 Key: HIVE-3309
 URL: https://issues.apache.org/jira/browse/HIVE-3309
 Project: Hive
  Issue Type: Bug
  Components: Metastore, Query Processor
Affects Versions: 0.10.0, 0.9.1
 Environment: SuSE 11 SP 1
 Hadoop Cluster + Hive
Reporter: rohithsharma
Priority: Minor
  Labels: patch
 Fix For: 0.10.0

 Attachments: HIVE-3309.patch


 There is still problem in drop partition columns if the partition columns 
 are mixture of string and non-string.
 There is behavioural change after fixing HIVE-3063.
 Before fix
 ==
 create table ptestfilter (a string, b int) partitioned by (c string, d int);
 alter table ptestfilter add partition (c='1', d=2);
 alter table ptestFilter add partition (c='2', d=1);
 alter table ptestfilter drop partition (c'2'); //this will execute fine
 After fix
 ==
 create table ptestfilter (a string, b int) partitioned by (c string, d int);
 alter table ptestfilter add partition (c='1', d=2);
 alter table ptestFilter add partition (c='2', d=1);
 alter table ptestfilter drop partition (c'2'); //this will fail to execute.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (HIVE-3309) drop partition doesnot work for mixture of string and non-string columns for non-equality operatior

2012-07-27 Thread rohithsharma (JIRA)

rohithsharma created HIVE-3309:
--

 Summary: drop partition doesnot work for mixture of string and 
non-string columns for non-equality operatior
 Key: HIVE-3309
 URL: https://issues.apache.org/jira/browse/HIVE-3309
 Project: Hive
  Issue Type: Bug
  Components: Metastore, Query Processor
Affects Versions: 0.9.1
 Environment: SuSE 11 SP 1
Hadoop Cluster + Hive
Reporter: rohithsharma
Priority: Minor


There is still problem in drop partition columns if the partition columns are 
mixture of string and non-string.

There is behavioural change after fixing HIVE-3063.
Before fix
==
create table ptestfilter (a string, b int) partitioned by (c string, d int);
alter table ptestfilter add partition (c='1', d=2);
alter table ptestFilter add partition (c='2', d=1);
alter table ptestfilter drop partition (c'2'); //this will execute fine

After fix
==
create table ptestfilter (a string, b int) partitioned by (c string, d int);
alter table ptestfilter add partition (c='1', d=2);
alter table ptestFilter add partition (c='2', d=1);
alter table ptestfilter drop partition (c'2'); //this will fail to execute.


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HIVE-3309) drop partition doesnot work for mixture of string and non-string columns for non-equality operatior

2012-07-27 Thread rohithsharma (JIRA)


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

rohithsharma commented on HIVE-3309:


bq. Which version of Hive are you using.?
I am using brahcn-0.9.1. HIVE-3076 is merged to this branch.



 drop partition doesnot work for mixture of string and non-string columns for 
 non-equality operatior
 ---

 Key: HIVE-3309
 URL: https://issues.apache.org/jira/browse/HIVE-3309
 Project: Hive
  Issue Type: Bug
  Components: Metastore, Query Processor
Affects Versions: 0.9.1
 Environment: SuSE 11 SP 1
 Hadoop Cluster + Hive
Reporter: rohithsharma
Priority: Minor

 There is still problem in drop partition columns if the partition columns 
 are mixture of string and non-string.
 There is behavioural change after fixing HIVE-3063.
 Before fix
 ==
 create table ptestfilter (a string, b int) partitioned by (c string, d int);
 alter table ptestfilter add partition (c='1', d=2);
 alter table ptestFilter add partition (c='2', d=1);
 alter table ptestfilter drop partition (c'2'); //this will execute fine
 After fix
 ==
 create table ptestfilter (a string, b int) partitioned by (c string, d int);
 alter table ptestfilter add partition (c='1', d=2);
 alter table ptestFilter add partition (c='2', d=1);
 alter table ptestfilter drop partition (c'2'); //this will fail to execute.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HIVE-2804) Task log retrieval fails on Hadoop 0.23

2012-06-21 Thread rohithsharma (JIRA)


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

rohithsharma commented on HIVE-2804:


In TaskLogProcessor.java, there are 2 methods which construct URL. One is 
getError() and another is getStackTraces(). TaskLogProcessor.getStackTraces() 
is called only if 'hive.exec.job.debug.capture.stacktraces' is set to true.I 
think in your case this was not set false.

 Task log retrieval fails on Hadoop 0.23
 ---

 Key: HIVE-2804
 URL: https://issues.apache.org/jira/browse/HIVE-2804
 Project: Hive
  Issue Type: Bug
  Components: Diagnosability, Query Processor, Security
Reporter: Carl Steinbach
Assignee: Zhenxiao Luo
 Attachments: HIVE-2804.1.patch.txt, HIVE-2804.2.patch.txt, 
 HIVE-2804.3.patch.txt, HIVE-2804.4.patch.txt, HIVE-2804.5.patch.txt, 
 HIVE-2804.5.patch.txt, HIVE-2804.6.patch.txt, HIVE-2804.7.patch.txt, 
 HIVE-2804.D3057.1.patch, HIVE-2804.D3057.2.patch, HIVE-2804.D3057.3.patch, 
 HIVE-2804.D3219.1.patch, HIVE-2804.D3219.2.patch




--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (HIVE-3170) Failed Job URL should be depends on MR cluster used.

2012-06-21 Thread rohithsharma (JIRA)

rohithsharma created HIVE-3170:
--

 Summary: Failed Job URL should be depends on MR cluster used.
 Key: HIVE-3170
 URL: https://issues.apache.org/jira/browse/HIVE-3170
 Project: Hive
  Issue Type: Bug
  Components: Diagnosability
Affects Versions: 0.10.0, 0.9.1
 Environment: Hive-Trunk + Hadoop-0.23.0
Reporter: rohithsharma


Once job is failed, the debug information displays URL to find failed job 
errors.
This URL should be depends on MR cluster used.
Currently,we dont find this URL in MR2 cluster.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HIVE-2804) Task log retrieval fails on Hadoop 0.23


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

rohithsharma commented on HIVE-2804:


I also encountered the same problem with hive UDAF queries such as PERCENTILE 
and ASSERT_TRUE. I have applied given patch and run these 2 queries. This patch 
fails throwing following excetiption.
{noformat}
Error during job, obtaining debugging information...
Examining task ID: task_1340014683209_0037_m_00 (and more) from job 
job_1340014683209_0037
Exception in thread Thread-26 java.lang.RuntimeException: Bad task log url
at 
org.apache.hadoop.hive.ql.exec.errors.TaskLogProcessor.getStackTraces(TaskLogProcessor.java:193)
at 
org.apache.hadoop.hive.ql.exec.JobDebugger.showJobFailDebugInfo(JobDebugger.java:227)
at org.apache.hadoop.hive.ql.exec.JobDebugger.run(JobDebugger.java:94)
at java.lang.Thread.run(Thread.java:662)
Caused by: java.net.MalformedURLException
at java.net.URL.init(URL.java:601)
at java.net.URL.init(URL.java:464)
at java.net.URL.init(URL.java:413)
at 
org.apache.hadoop.hive.ql.exec.errors.TaskLogProcessor.getStackTraces(TaskLogProcessor.java:191)
... 3 more
{noformat}

Correct me if I am wrong ,
With my understanding problem is adding URI's into 'taskLogUrls', I feel we 
need null check while adding URI into 'taskLogUrls'  because hadoop23shims 
returns null if the cluster is MR2. This URI construction fails since null is 
passed as argument when TaskLogProcessor.getErrors() or 
TaskLogProcessor.getStackTraces() is called and throws MalformedURLException.

 Task log retrieval fails on Hadoop 0.23
 ---

 Key: HIVE-2804
 URL: https://issues.apache.org/jira/browse/HIVE-2804
 Project: Hive
  Issue Type: Bug
  Components: Diagnosability, Query Processor, Security
Reporter: Carl Steinbach
Assignee: Zhenxiao Luo
 Attachments: HIVE-2804.1.patch.txt, HIVE-2804.2.patch.txt, 
 HIVE-2804.3.patch.txt, HIVE-2804.4.patch.txt, HIVE-2804.5.patch.txt, 
 HIVE-2804.5.patch.txt, HIVE-2804.6.patch.txt, HIVE-2804.D3057.1.patch, 
 HIVE-2804.D3057.2.patch, HIVE-2804.D3057.3.patch, HIVE-2804.D3219.1.patch, 
 HIVE-2804.D3219.2.patch




--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HIVE-2804) Task log retrieval fails on Hadoop 0.23


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

rohithsharma commented on HIVE-2804:


In addition to above, 

Currently, Once the job is failed, debug information is displayed along with 
URL. This 'taskUrl' displayed is specific to MR1 cluster. This 'taskUrl' 
construction should be based on MR cluster.

 Task log retrieval fails on Hadoop 0.23
 ---

 Key: HIVE-2804
 URL: https://issues.apache.org/jira/browse/HIVE-2804
 Project: Hive
  Issue Type: Bug
  Components: Diagnosability, Query Processor, Security
Reporter: Carl Steinbach
Assignee: Zhenxiao Luo
 Attachments: HIVE-2804.1.patch.txt, HIVE-2804.2.patch.txt, 
 HIVE-2804.3.patch.txt, HIVE-2804.4.patch.txt, HIVE-2804.5.patch.txt, 
 HIVE-2804.5.patch.txt, HIVE-2804.6.patch.txt, HIVE-2804.D3057.1.patch, 
 HIVE-2804.D3057.2.patch, HIVE-2804.D3057.3.patch, HIVE-2804.D3219.1.patch, 
 HIVE-2804.D3219.2.patch




--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HIVE-2804) Task log retrieval fails on Hadoop 0.23


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

rohithsharma commented on HIVE-2804:


@zhenxiao
 Are you using MR1 or MR2 to reproduce the exception?
I am using MR2 cluster.

Latest patch solved the problem, Thanks you :-)

 Task log retrieval fails on Hadoop 0.23
 ---

 Key: HIVE-2804
 URL: https://issues.apache.org/jira/browse/HIVE-2804
 Project: Hive
  Issue Type: Bug
  Components: Diagnosability, Query Processor, Security
Reporter: Carl Steinbach
Assignee: Zhenxiao Luo
 Attachments: HIVE-2804.1.patch.txt, HIVE-2804.2.patch.txt, 
 HIVE-2804.3.patch.txt, HIVE-2804.4.patch.txt, HIVE-2804.5.patch.txt, 
 HIVE-2804.5.patch.txt, HIVE-2804.6.patch.txt, HIVE-2804.7.patch.txt, 
 HIVE-2804.D3057.1.patch, HIVE-2804.D3057.2.patch, HIVE-2804.D3057.3.patch, 
 HIVE-2804.D3219.1.patch, HIVE-2804.D3219.2.patch




--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HIVE-2804) Task log retrieval fails on Hadoop 0.23


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

rohithsharma commented on HIVE-2804:


I think, 
adding GenericUDFEvaluateNPE.java only for test framework is not required. 
Existing below UDAF queries will catch above problem.
 SELECT percentile(key,5) FROM src;
 SELECT assert_true(key = 100) FROM src;

We can add these queries into tests.


 Task log retrieval fails on Hadoop 0.23
 ---

 Key: HIVE-2804
 URL: https://issues.apache.org/jira/browse/HIVE-2804
 Project: Hive
  Issue Type: Bug
  Components: Diagnosability, Query Processor, Security
Reporter: Carl Steinbach
Assignee: Zhenxiao Luo
 Attachments: HIVE-2804.1.patch.txt, HIVE-2804.2.patch.txt, 
 HIVE-2804.3.patch.txt, HIVE-2804.4.patch.txt, HIVE-2804.5.patch.txt, 
 HIVE-2804.5.patch.txt, HIVE-2804.6.patch.txt, HIVE-2804.7.patch.txt, 
 HIVE-2804.D3057.1.patch, HIVE-2804.D3057.2.patch, HIVE-2804.D3057.3.patch, 
 HIVE-2804.D3219.1.patch, HIVE-2804.D3219.2.patch




--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (HIVE-3156) Support MiniMR tests for Hadoop-0.23

2012-06-19 Thread rohithsharma (JIRA)

rohithsharma created HIVE-3156:
--

 Summary: Support MiniMR tests for Hadoop-0.23
 Key: HIVE-3156
 URL: https://issues.apache.org/jira/browse/HIVE-3156
 Project: Hive
  Issue Type: Bug
  Components: Tests
Affects Versions: 0.9.1
 Environment: Hive-0.9.1 + Hadoop-0.23.0
Reporter: rohithsharma


When MiniMR tests are ran with hadoop-0.23.0, tests fails throwing following 
exception.

java.lang.UnsupportedOperationException
at 
org.apache.hadoop.mapred.MiniMRCluster.getJobTrackerPort(MiniMRCluster.java:88)
at org.apache.hadoop.hive.ql.QTestUtil.initConf(QTestUtil.java:215)


In hadoop-0.23 ,few mapreduce API's are not supported like getJobTrackerPort(). 

Here, we need to use API's based on hadoop versions.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HIVE-3151) Not able to configure HIVE_OPTS.

2012-06-19 Thread rohithsharma (JIRA)


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

rohithsharma commented on HIVE-3151:


I tried with passing these arguments through HADOOP_OPTS from hive scripts. 
Unfortunately this doesnot work because HADOOP_OPTS is nullified in 
hadoop-env.sh.

 Not able to configure HIVE_OPTS.
 

 Key: HIVE-3151
 URL: https://issues.apache.org/jira/browse/HIVE-3151
 Project: Hive
  Issue Type: Bug
  Components: Configuration
Affects Versions: 0.10.0, 0.9.1
 Environment: Hadoop-0.23.0 + Hive-0.9.1
Reporter: rohithsharma

 Parameters like GC_OPTS, DEBUG_OPTS that need to passed for hive for getting 
 gc 
 information and debugging hive respectively. 
 When I configure HIVE_OPTS, hive server is not starting.
 Following way HIVE_OPTS  are set in 
 1, I added below parameters to hive_opts in $HIVE_HOME/bin/hive script.
 GC_OPTS=$GC_OPTS -Xloggc:/home/hive-0.9.0/gcHiveLog.log
 export HIVE_OPTS=$HIVE_OPTS $GC_OPTS
 2. I passed hive_opts $HIVE_HOME/bin/ext/hiveserver.sh script.
 exec $HADOOP jar $JAR $CLASS $HIVE_OPTS $@

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (HIVE-3151) Not able to configure HIVE_OPTS.

2012-06-18 Thread rohithsharma (JIRA)

rohithsharma created HIVE-3151:
--

 Summary: Not able to configure HIVE_OPTS.
 Key: HIVE-3151
 URL: https://issues.apache.org/jira/browse/HIVE-3151
 Project: Hive
  Issue Type: Bug
  Components: Configuration
Affects Versions: 0.10.0, 0.9.1
 Environment: Hadoop-0.23.0 + Hive-0.9.1
Reporter: rohithsharma


Parameters like GC_OPTS, DEBUG_OPTS that need to passed for hive for getting gc 

information and debugging hive respectively. 

When I configure HIVE_OPTS, hive server is not starting.

Following way HIVE_OPTS  are set in 

1, I added below parameters to hive_opts in $HIVE_HOME/bin/hive script.

GC_OPTS=$GC_OPTS -Xloggc:/home/hive-0.9.0/gcHiveLog.log
export HIVE_OPTS=$HIVE_OPTS $GC_OPTS

2. I passed hive_opts $HIVE_HOME/bin/ext/hiveserver.sh script.
exec $HADOOP jar $JAR $CLASS $HIVE_OPTS $@






--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HIVE-3143) Following Test Cases fails in Hive-0.9 and Hadoop-0.23

2012-06-18 Thread rohithsharma (JIRA)


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

rohithsharma commented on HIVE-3143:


org.apache.hadoop.hive.cli.TestCliDriver.testCliDriver_join14
org.apache.hadoop.hive.cli.TestCliDriver.testCliDriver_sample_islocalmode_hook
org.apache.hadoop.hive.cli.TestNegativeCliDriver.testNegativeCliDriver_autolocal1

Above set of test cases throw following exception.
{noformat}
java.io.IOException: Cannot initialize Cluster. Please check your configuration 
for mapreduce.framework.name and the correspond server addresses.
at org.apache.hadoop.mapreduce.Cluster.initialize(Cluster.java:121) 
 
at org.apache.hadoop.mapreduce.Cluster.init(Cluster.java:83)  
 
at org.apache.hadoop.mapreduce.Cluster.init(Cluster.java:76)  
 
at org.apache.hadoop.mapred.JobClient.init(JobClient.java:487)  
 
at org.apache.hadoop.mapred.JobClient.init(JobClient.java:466)
 
at org.apache.hadoop.hive.ql.exec.ExecDriver.execute(ExecDriver.java:418)   
 
at org.apache.hadoop.hive.ql.exec.MapRedTask.execute(MapRedTask.java:137)   
 
at org.apache.hadoop.hive.ql.exec.Task.executeTask(Task.java:135)   
 
at 
org.apache.hadoop.hive.ql.exec.TaskRunner.runSequential(TaskRunner.java:57) 
  
at org.apache.hadoop.hive.ql.Driver.launchTask(Driver.java:1329)
 
{noformat}



 Following Test Cases fails in Hive-0.9 and Hadoop-0.23
 --

 Key: HIVE-3143
 URL: https://issues.apache.org/jira/browse/HIVE-3143
 Project: Hive
  Issue Type: Bug
  Components: Tests
Affects Versions: 0.9.1
 Environment: Hadoop-2.0.1
Reporter: rohithsharma

 When I run Hive-0.9.1 with hadoop-0.23, below test cases are consistently 
 failed.
 TestHBaseMinimrCliDriver.testCliDriver_hbase_bulk 
 TestCliDriver.testCliDriver_archive 
 TestCliDriver.testCliDriver_archive_corrupt 
 TestCliDriver.testCliDriver_archive_multi 
 TestCliDriver.testCliDriver_join14 
 TestCliDriver.testCliDriver_query_properties 
 TestCliDriver.testCliDriver_sample_islocalmode_hook 
 TestCliDriver.testCliDriver_split_sample 
 TestNegativeCliDriver.testNegativeCliDriver_autolocal1 
 TestNegativeCliDriver.testNegativeCliDriver_local_mapred_error_cache 
 TestMinimrCliDriver 
 TestNegativeMinimrCliDriver

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (HIVE-3141) Bug in SELECT query

2012-06-15 Thread rohithsharma (JIRA)


 [ 
https://issues.apache.org/jira/browse/HIVE-3141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

rohithsharma updated HIVE-3141:
---

Component/s: (was: CLI)
 Tests

 Bug in SELECT query
 ---

 Key: HIVE-3141
 URL: https://issues.apache.org/jira/browse/HIVE-3141
 Project: Hive
  Issue Type: Bug
  Components: Tests
 Environment: OS: Ubuntu 
 Hive version: hive-0.7.1-cdh3u2
 Hadoop : hadoop-0.20.2
Reporter: ASK

 When i use ' select *(followed by any alphan-numeric character) frm table , 
 query is throwing some issues. It display the result for select *
 It doesnot happen when only numbers follow the *

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (HIVE-3143) Following Test Cases fails in Hive-0.9 and Hadoop-0.23

2012-06-15 Thread rohithsharma (JIRA)

rohithsharma created HIVE-3143:
--

 Summary: Following Test Cases fails in Hive-0.9 and Hadoop-0.23
 Key: HIVE-3143
 URL: https://issues.apache.org/jira/browse/HIVE-3143
 Project: Hive
  Issue Type: Bug
  Components: Tests
Affects Versions: 0.9.1
 Environment: Hadoop-2.0.1
Reporter: rohithsharma


When I run Hive-0.9.1 with hadoop-0.23, below test cases are consistently 
failed.

TestHBaseMinimrCliDriver.testCliDriver_hbase_bulk 
TestCliDriver.testCliDriver_archive 
TestCliDriver.testCliDriver_archive_corrupt 
TestCliDriver.testCliDriver_archive_multi 
TestCliDriver.testCliDriver_join14 
TestCliDriver.testCliDriver_query_properties 
TestCliDriver.testCliDriver_sample_islocalmode_hook 
TestCliDriver.testCliDriver_split_sample 
TestNegativeCliDriver.testNegativeCliDriver_autolocal1 
TestNegativeCliDriver.testNegativeCliDriver_local_mapred_error_cache 
TestMinimrCliDriver 
TestNegativeMinimrCliDriver

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (HIVE-3141) Bug in SELECT query

2012-06-15 Thread rohithsharma (JIRA)


 [ 
https://issues.apache.org/jira/browse/HIVE-3141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

rohithsharma updated HIVE-3141:
---

Component/s: (was: Tests)
 CLI

 Bug in SELECT query
 ---

 Key: HIVE-3141
 URL: https://issues.apache.org/jira/browse/HIVE-3141
 Project: Hive
  Issue Type: Bug
  Components: CLI
 Environment: OS: Ubuntu 
 Hive version: hive-0.7.1-cdh3u2
 Hadoop : hadoop-0.20.2
Reporter: ASK

 When i use ' select *(followed by any alphan-numeric character) frm table , 
 query is throwing some issues. It display the result for select *
 It doesnot happen when only numbers follow the *

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (HIVE-3091) Fix eclipse classpath for hadoop-2.0.1 support

2012-06-05 Thread rohithsharma (JIRA)

rohithsharma created HIVE-3091:
--

 Summary: Fix eclipse classpath for hadoop-2.0.1 support
 Key: HIVE-3091
 URL: https://issues.apache.org/jira/browse/HIVE-3091
 Project: Hive
  Issue Type: Bug
  Components: Build Infrastructure
Affects Versions: 0.10.0, 0.9.1
Reporter: rohithsharma


Hive support different versions of hadoop such as 0.20,0.20S(1.0.0) and 
0.23.0(2.0.1). When we build hive with hadoop-0.23(2.0.1), we get compilation 
error in eclipse because it is refering to 0.20.0 hadoop jars.

Currently, hive classpath is generated with pre-defined eclipse template.This 
template support only for 0.20 version of hadoop. This is causing compilation 
error in eclipse.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HIVE-3091) Fix eclipse classpath for hadoop-2.0.1 support

2012-06-05 Thread rohithsharma (JIRA)

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

rohithsharma commented on HIVE-3091:

I have 2 approached to handle this problem.

1. Maitain differnt eclipse template for different version of hadoop.

2. Make current eclipse template as generic such a way that all the tokens in
the template is replaced with value.

I suggest for first approach because different hadoop version require differnt
version of dependent jar.
For example hadooop-0.20 require common-codec-1.3.jar where hadoop-0.23.0
require common-codec-1.4.jar.

Fix eclipse classpath for hadoop-2.0.1 support
--

Key: HIVE-3091
URL: https://issues.apache.org/jira/browse/HIVE-3091
Project: Hive
Issue Type: Bug
Components: Build Infrastructure
Affects Versions: 0.10.0, 0.9.1
Reporter: rohithsharma

Hive support different versions of hadoop such as 0.20,0.20S(1.0.0) and
0.23.0(2.0.1). When we build hive with hadoop-0.23(2.0.1), we get compilation
error in eclipse because it is refering to 0.20.0 hadoop jars.
Currently, hive classpath is generated with pre-defined eclipse template.This
template support only for 0.20 version of hadoop. This is causing compilation
error in eclipse.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HIVE-3060) ClassNotFoundError while executing the getClusterStatus API

2012-06-04 Thread rohithsharma (JIRA)


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

rohithsharma commented on HIVE-3060:


I verified with patch. It is working fine. Please duplicate this issue. Thanks 
:-)

 ClassNotFoundError while executing the getClusterStatus API
 ---

 Key: HIVE-3060
 URL: https://issues.apache.org/jira/browse/HIVE-3060
 Project: Hive
  Issue Type: Bug
  Components: Shims
Affects Versions: 0.9.0
Reporter: Kristam Subba Swathi

 Please find the exception trace
 
 {noformat}
 Exception in thread pool-1-thread-3 java.lang.NoClassDefFoundError: 
 org/apache/hadoop/mapred/JobTracker$State
   at 
 org.apache.hadoop.hive.shims.Hadoop20SShims$2.clinit(Hadoop20SShims.java:35)
   at 
 org.apache.hadoop.hive.shims.Hadoop20SShims.getJobTrackerState(Hadoop20SShims.java:35)
   at 
 org.apache.hadoop.hive.service.HiveServer$HiveServerHandler.getClusterStatus(HiveServer.java:244)
   at 
 org.apache.hadoop.hive.service.ThriftHive$Processor$getClusterStatus.getResult(ThriftHive.java:749)
   at 
 org.apache.hadoop.hive.service.ThriftHive$Processor$getClusterStatus.getResult(ThriftHive.java:737)
   at org.apache.thrift.ProcessFunction.process(ProcessFunction.java:32)
   at org.apache.thrift.TBaseProcessor.process(TBaseProcessor.java:34)
   at 
 org.apache.thrift.server.TThreadPoolServer$WorkerProcess.run(TThreadPoolServer.java:176)
   at 
 java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
   at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
   at java.lang.Thread.run(Thread.java:662)
 Caused by: java.lang.ClassNotFoundException: 
 org.apache.hadoop.mapred.JobTracker$State
   at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
   at java.security.AccessController.doPrivileged(Native Method)
   at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
   at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
 {noformat}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HIVE-3060) ClassNotFoundError while executing the getClusterStatus API

2012-05-27 Thread rohithsharma (JIRA)


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

rohithsharma commented on HIVE-3060:


This exception is thrown when Hive-0.9.0 is deployed with Hadoop-X.0.0 where X 
 0. 

Reason for above exception,
Hive loads 0.20,0.20S and 0.23 version of hadoopshims. We get hadoop 
version from classpath VersionInfo.getVersion() is 2.0.0-SNAPSHOT. But 
returning 0.20S if X  0. 

Correct me If I am wrong,
As hadoop-0.23 name is same as hadoop-2.0.0, hive should support for 
hadoop-2.0.0. i.e we need to add haddop shims for hadoop-2.0.0.

 ClassNotFoundError while executing the getClusterStatus API
 ---

 Key: HIVE-3060
 URL: https://issues.apache.org/jira/browse/HIVE-3060
 Project: Hive
  Issue Type: Bug
  Components: Shims
Affects Versions: 0.9.0
Reporter: Kristam Subba Swathi

 Please find the exception trace
 
 {noformat}
 Exception in thread pool-1-thread-3 java.lang.NoClassDefFoundError: 
 org/apache/hadoop/mapred/JobTracker$State
   at 
 org.apache.hadoop.hive.shims.Hadoop20SShims$2.clinit(Hadoop20SShims.java:35)
   at 
 org.apache.hadoop.hive.shims.Hadoop20SShims.getJobTrackerState(Hadoop20SShims.java:35)
   at 
 org.apache.hadoop.hive.service.HiveServer$HiveServerHandler.getClusterStatus(HiveServer.java:244)
   at 
 org.apache.hadoop.hive.service.ThriftHive$Processor$getClusterStatus.getResult(ThriftHive.java:749)
   at 
 org.apache.hadoop.hive.service.ThriftHive$Processor$getClusterStatus.getResult(ThriftHive.java:737)
   at org.apache.thrift.ProcessFunction.process(ProcessFunction.java:32)
   at org.apache.thrift.TBaseProcessor.process(TBaseProcessor.java:34)
   at 
 org.apache.thrift.server.TThreadPoolServer$WorkerProcess.run(TThreadPoolServer.java:176)
   at 
 java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
   at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
   at java.lang.Thread.run(Thread.java:662)
 Caused by: java.lang.ClassNotFoundException: 
 org.apache.hadoop.mapred.JobTracker$State
   at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
   at java.security.AccessController.doPrivileged(Native Method)
   at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
   at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
 {noformat}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (HIVE-2271) InConsistency between Infomation Document and Actual Behavior for Built In Aggregate Functions(UDAF) Return Type.

2011-07-07 Thread rohithsharma (JIRA)

InConsistency between Infomation Document and Actual Behavior for Built In 
Aggregate Functions(UDAF) Return Type. 
--

 Key: HIVE-2271
 URL: https://issues.apache.org/jira/browse/HIVE-2271
 Project: Hive
  Issue Type: Bug
  Components: Documentation, Query Processor
Affects Versions: 0.7.1, 0.7.0, 0.6.0, 0.5.0
 Environment: SuSE-Linux-11
Reporter: rohithsharma


I followed the Information Document for executing UDAF like 
MIN(),MAX(),SUM(),AVG() and COUNT() below link.

[https://cwiki.apache.org/confluence/display/Hive/LanguageManual+UDF#LanguageManualUDF-BuiltinAggregateFunctions%28UDAF%29]
 

Observed mismatch for RETURN TYPE mentioned in Information Document and Actual 
Behavior.

1.) Return Type for min(colName),max(colName) is mentioned as DOUBLE,but while 
retrieving it is returning colName DataType passed to Min()/Max().


Ex:
1).create table test(a int,b smallint,c string);
2).select min(a) from test;
3).ResultSet.getMetaData ().getColumnTypeName ( 1 )
  Output : int
  Expected : double(According to InformationDoc)


2.) Return Type for sum(colName) is mentioned as DOUBLE,but while retrieving it 
is always returning as BIGINT

Ex:
1).create table test(a int,b smallint,c string);
2).select sum(a) from test;
3).ResultSet.getMetaData ().getColumnTypeName ( 1 )
  Output : BIGINT
  Expected : double(According to InformationDoc)









--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (HIVE-2263) Wrong value is retrieved by ResultSet.getColumnDisplaySize() for SMALLINT and FLOAT Datatype

Wrong value is retrieved by ResultSet.getColumnDisplaySize() for SMALLINT and 
FLOAT Datatype


 Key: HIVE-2263
 URL: https://issues.apache.org/jira/browse/HIVE-2263
 Project: Hive
  Issue Type: Bug
  Components: JDBC
Affects Versions: 0.7.1, 0.5.0
 Environment: Linux. Hadoop-20.1 and Hive-0.7.1
Reporter: rohithsharma
Priority: Minor



1).Create a table with smallint datatype.
create table test(a smallint,b int,c bigint);
2).ResultSet result = select a,b,c from test;
3) When I Try to get the getColumnDisplaySize()for the columns,
i.e   ResultSet.getColumnDisplaySize(a) is 32 (default vaule  )  
  ResultSet.getColumnDisplaySize(b) is 16   
  ResultSet.getColumnDisplaySize(c) is 32 

But in the code, default is returning.
{noformat}
public int getColumnDisplaySize(int column) throws SQLException {
// taking a stab at appropriate values
switch (getColumnType(column)) {
case Types.VARCHAR:
case Types.BIGINT:
  return 32;
case Types.TINYINT:
  return 2;
case Types.BOOLEAN:
  return 8;
case Types.DOUBLE:
case Types.INTEGER:
  return 16;
default:
  return 32;
}
  }
{noformat}
  

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (HIVE-2264) Hive server is SHUTTING DOWN when invalid/complex queries been used.

Hive server is SHUTTING DOWN when invalid/complex queries been used.


 Key: HIVE-2264
 URL: https://issues.apache.org/jira/browse/HIVE-2264
 Project: Hive
  Issue Type: Bug
  Components: Query Processor
Affects Versions: 0.7.1, 0.7.0
 Environment: SuSE-Linux-11
Reporter: rohithsharma
Priority: Critical


When invalid query is beeing executed, Hive server is shutting down.

{noformat}
CREATE TABLE SAMPLETABLE(IP STRING , showtime BIGINT ) partitioned by (ds 
string,ipz int) ROW FORMAT DELIMITED FIELDS TERMINATED BY '\040'

ALTER TABLE SAMPLETABLE add Partition(ds='sf') location '/user/hive/warehouse' 
Partition(ipz=100) location '/user/hive/warehouse'
{noformat}



--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (HIVE-2264) Hive server is SHUTTING DOWN when invalid/complex queries been used.


 [ 
https://issues.apache.org/jira/browse/HIVE-2264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

rohithsharma updated HIVE-2264:
---

Description: 
When invalid query is beeing executed, Hive server is shutting down.

{noformat}
CREATE TABLE SAMPLETABLE(IP STRING , showtime BIGINT ) partitioned by (ds 
string,ipz int) ROW FORMAT DELIMITED FIELDS TERMINATED BY '\040'

ALTER TABLE SAMPLETABLE add Partition(ds='sf') location '/user/hive/warehouse' 
Partition(ipz=100) location '/user/hive/warehouse'
{noformat}

  was:
When invalid query is beeing executed, Hive server is shutting down.

{noformat}
CREATE TABLE SAMPLETABLE(IP STRING , showtime BIGINT ) partitioned by (ds 
string,ipz int) ROW FORMAT DELIMITED FIELDS TERMINATED BY '\040'

ALTER TABLE SAMPLETABLE add Partition(ds='sf') location '/user/hive/warehouse' 
Partition(ipz=100) location '/user/hive/warehouse'
{noformat}




 Hive server is SHUTTING DOWN when invalid/complex queries been used.
 

 Key: HIVE-2264
 URL: https://issues.apache.org/jira/browse/HIVE-2264
 Project: Hive
  Issue Type: Bug
  Components: Query Processor
Affects Versions: 0.7.0, 0.7.1
 Environment: SuSE-Linux-11
Reporter: rohithsharma
Priority: Critical

 When invalid query is beeing executed, Hive server is shutting down.
 {noformat}
 CREATE TABLE SAMPLETABLE(IP STRING , showtime BIGINT ) partitioned by (ds 
 string,ipz int) ROW FORMAT DELIMITED FIELDS TERMINATED BY '\040'
 ALTER TABLE SAMPLETABLE add Partition(ds='sf') location 
 '/user/hive/warehouse' Partition(ipz=100) location '/user/hive/warehouse'
 {noformat}

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (HIVE-2264) Hive server is SHUTTING DOWN when invalid queries beeing executed.


 [ 
https://issues.apache.org/jira/browse/HIVE-2264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

rohithsharma updated HIVE-2264:
---

Summary: Hive server is SHUTTING DOWN when invalid queries beeing executed. 
 (was: Hive server is SHUTTING DOWN when invalid/complex queries been used.)

 Hive server is SHUTTING DOWN when invalid queries beeing executed.
 --

 Key: HIVE-2264
 URL: https://issues.apache.org/jira/browse/HIVE-2264
 Project: Hive
  Issue Type: Bug
  Components: Query Processor
Affects Versions: 0.7.0, 0.7.1
 Environment: SuSE-Linux-11
Reporter: rohithsharma
Priority: Critical

 When invalid query is beeing executed, Hive server is shutting down.
 {noformat}
 CREATE TABLE SAMPLETABLE(IP STRING , showtime BIGINT ) partitioned by (ds 
 string,ipz int) ROW FORMAT DELIMITED FIELDS TERMINATED BY '\040'
 ALTER TABLE SAMPLETABLE add Partition(ds='sf') location 
 '/user/hive/warehouse' Partition(ipz=100) location '/user/hive/warehouse'
 {noformat}

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (HIVE-2265) insert overwrite directory for Multilevel directory fails.