[jira] [Commented] (HIVE-3610) Add a command "Explain dependency ..."

[Kevin Wilfong (JIRA)]

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

Kevin Wilfong commented on HIVE-3610:
-

+1 Thanks Sambavi

> Add a command "Explain dependency ..."
> --
>
> Key: HIVE-3610
> URL: https://issues.apache.org/jira/browse/HIVE-3610
> Project: Hive
>  Issue Type: New Feature
>  Components: Query Processor
>Affects Versions: 0.9.0
>Reporter: Sambavi Muthukrishnan
>Assignee: Sambavi Muthukrishnan
>Priority: Minor
> Attachments: explain_dependency.1.patch, explain_dependency.2.patch
>
>
> Add a new command "EXPLAIN DEPENDENCY".
> Any query can be passed to EXPLAIN DEPENDENCY as with EXPLAIN 
> (FORMATTED/EXTENDED). The output of this command will be JSON that provides 
> the list of tables and partitions that the query depends on.
> One possible use case is to determine the set of tables/views that are used 
> by a view, and the set of partitions that are used by a given query on that 
> view. This will allow a view to be replicated from one Hive instance to 
> another, since we can determine the set of objects that need to be replicated 
> for replication of the view to be successful.
> Example output:
> {"input_tables":[{"tablename": "default@test_sambavi_v2", "tabletype": 
> "EXTERNAL_TABLE"}, {"tablename": "default@test_sambavi_v1", "tabletype": 
> "TABLE"}], "input 
> partitions":["default@srcpart@ds=2008-04-08/hr=11","default@srcpart@ds=2008-04-08/hr=12"]}

--
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-3610) Add a command "Explain dependency ..."

[Sambavi Muthukrishnan (JIRA)]

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

Sambavi Muthukrishnan updated HIVE-3610:


Attachment: explain_dependency.2.patch

> Add a command "Explain dependency ..."
> --
>
> Key: HIVE-3610
> URL: https://issues.apache.org/jira/browse/HIVE-3610
> Project: Hive
>  Issue Type: New Feature
>  Components: Query Processor
>Affects Versions: 0.9.0
>Reporter: Sambavi Muthukrishnan
>Assignee: Sambavi Muthukrishnan
>Priority: Minor
> Attachments: explain_dependency.1.patch, explain_dependency.2.patch
>
>
> Add a new command "EXPLAIN DEPENDENCY".
> Any query can be passed to EXPLAIN DEPENDENCY as with EXPLAIN 
> (FORMATTED/EXTENDED). The output of this command will be JSON that provides 
> the list of tables and partitions that the query depends on.
> One possible use case is to determine the set of tables/views that are used 
> by a view, and the set of partitions that are used by a given query on that 
> view. This will allow a view to be replicated from one Hive instance to 
> another, since we can determine the set of objects that need to be replicated 
> for replication of the view to be successful.
> Example output:
> {"input_tables":[{"tablename": "default@test_sambavi_v2", "tabletype": 
> "EXTERNAL_TABLE"}, {"tablename": "default@test_sambavi_v1", "tabletype": 
> "TABLE"}], "input 
> partitions":["default@srcpart@ds=2008-04-08/hr=11","default@srcpart@ds=2008-04-08/hr=12"]}

--
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-3610) Add a command "Explain dependency ..."

[Sambavi Muthukrishnan (JIRA)]

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

Sambavi Muthukrishnan commented on HIVE-3610:
-

Fixed for comments, added new patch.

> Add a command "Explain dependency ..."
> --
>
> Key: HIVE-3610
> URL: https://issues.apache.org/jira/browse/HIVE-3610
> Project: Hive
>  Issue Type: New Feature
>  Components: Query Processor
>Affects Versions: 0.9.0
>Reporter: Sambavi Muthukrishnan
>Assignee: Sambavi Muthukrishnan
>Priority: Minor
> Attachments: explain_dependency.1.patch, explain_dependency.2.patch
>
>
> Add a new command "EXPLAIN DEPENDENCY".
> Any query can be passed to EXPLAIN DEPENDENCY as with EXPLAIN 
> (FORMATTED/EXTENDED). The output of this command will be JSON that provides 
> the list of tables and partitions that the query depends on.
> One possible use case is to determine the set of tables/views that are used 
> by a view, and the set of partitions that are used by a given query on that 
> view. This will allow a view to be replicated from one Hive instance to 
> another, since we can determine the set of objects that need to be replicated 
> for replication of the view to be successful.
> Example output:
> {"input_tables":[{"tablename": "default@test_sambavi_v2", "tabletype": 
> "EXTERNAL_TABLE"}, {"tablename": "default@test_sambavi_v1", "tabletype": 
> "TABLE"}], "input 
> partitions":["default@srcpart@ds=2008-04-08/hr=11","default@srcpart@ds=2008-04-08/hr=12"]}

--
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-3626) RetryingHMSHandler should wrap JDOException inside MetaException

[Bhushan Mandhani (JIRA)]

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

Bhushan Mandhani commented on HIVE-3626:


Diff at https://reviews.facebook.net/D6255

> RetryingHMSHandler should wrap JDOException inside MetaException
> 
>
> Key: HIVE-3626
> URL: https://issues.apache.org/jira/browse/HIVE-3626
> Project: Hive
>  Issue Type: Improvement
>  Components: Metastore
>Reporter: Bhushan Mandhani
>Assignee: Bhushan Mandhani
>Priority: Minor
>
> RetryingHMSHandler catches and retries for JDOExceptions. If retry limit is 
> exceeded, it throws the caught JDOException. Instead it should wrap this up 
> in a MetaException. That way the error message and stack trace can be 
> successfully communicated back to the Hive Client by the Thrift host and the 
> client can show better error messages and log messages. Otherwise, everything 
> appears as a TException with no further debugging info. 

--
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-3626) RetryingHMSHandler should wrap JDOException inside MetaException

[Bhushan Mandhani (JIRA)]

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

Bhushan Mandhani updated HIVE-3626:
---

Status: Patch Available  (was: Open)

> RetryingHMSHandler should wrap JDOException inside MetaException
> 
>
> Key: HIVE-3626
> URL: https://issues.apache.org/jira/browse/HIVE-3626
> Project: Hive
>  Issue Type: Improvement
>  Components: Metastore
>Reporter: Bhushan Mandhani
>Assignee: Bhushan Mandhani
>Priority: Minor
>
> RetryingHMSHandler catches and retries for JDOExceptions. If retry limit is 
> exceeded, it throws the caught JDOException. Instead it should wrap this up 
> in a MetaException. That way the error message and stack trace can be 
> successfully communicated back to the Hive Client by the Thrift host and the 
> client can show better error messages and log messages. Otherwise, everything 
> appears as a TException with no further debugging info. 

--
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-3627) eclipse misses library: javolution-@javolution-version@.jar

[Gang Tim Liu (JIRA)]

Gang Tim Liu created HIVE-3627:
--

 Summary: eclipse misses library:  
javolution-@javolution-version@.jar
 Key: HIVE-3627
 URL: https://issues.apache.org/jira/browse/HIVE-3627
 Project: Hive
  Issue Type: Bug
  Components: Build Infrastructure
Reporter: Gang Tim Liu
Priority: Minor


After checking out the latest trunk, build eclipse project:

ant clean package eclipse-files

Then, import project to eclipse, you will see the error:

Description ResourcePathLocationType
Project 'hive-trunk-10-26' is missing required library: 
'build/ivy/lib/default/javolution-@javolution-version@.jar' 
hive-trunk-10-26Build path  Build Path Problem

--
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-2693) Add DECIMAL data type

[Josh Wills (JIRA)]

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

Josh Wills updated HIVE-2693:
-

Attachment: HIVE-2693-take4.patch

Latest and greatest.

> Add DECIMAL data type
> -
>
> Key: HIVE-2693
> URL: https://issues.apache.org/jira/browse/HIVE-2693
> Project: Hive
>  Issue Type: New Feature
>  Components: Query Processor, Types
>Reporter: Carl Steinbach
>Assignee: Prasad Mujumdar
> Attachments: HIVE-2693-all.patch, HIVE-2693-fix.patch, 
> HIVE-2693.patch, HIVE-2693-take3.patch, HIVE-2693-take4.patch
>
>
> Add support for the DECIMAL data type. HIVE-2272 (TIMESTAMP) provides a nice 
> template for how to do this.

--
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-3626) RetryingHMSHandler should wrap JDOException inside MetaException

[Bhushan Mandhani (JIRA)]

Bhushan Mandhani created HIVE-3626:
--

 Summary: RetryingHMSHandler should wrap JDOException inside 
MetaException
 Key: HIVE-3626
 URL: https://issues.apache.org/jira/browse/HIVE-3626
 Project: Hive
  Issue Type: Improvement
  Components: Metastore
Reporter: Bhushan Mandhani
Assignee: Bhushan Mandhani
Priority: Minor


RetryingHMSHandler catches and retries for JDOExceptions. If retry limit is 
exceeded, it throws the caught JDOException. Instead it should wrap this up in 
a MetaException. That way the error message and stack trace can be successfully 
communicated back to the Hive Client by the Thrift host and the client can show 
better error messages and log messages. Otherwise, everything appears as a 
TException with no further debugging info. 

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

Build failed in Jenkins: Hive-0.9.1-SNAPSHOT-h0.21 #179

[Apache Jenkins Server]

See 

--
[...truncated 36685 lines...]
[junit] POSTHOOK: query: select count(1) as cnt from testhivedrivertable
[junit] POSTHOOK: type: DROPTABLE
[junit] POSTHOOK: Input: default@testhivedrivertable
[junit] POSTHOOK: Output: 
file:/tmp/hudson/hive_2012-10-26_14-55-57_889_2034853096758285742/-mr-1
[junit] OK
[junit] PREHOOK: query: drop table testhivedrivertable
[junit] PREHOOK: type: DROPTABLE
[junit] PREHOOK: Input: default@testhivedrivertable
[junit] PREHOOK: Output: default@testhivedrivertable
[junit] POSTHOOK: query: drop table testhivedrivertable
[junit] POSTHOOK: type: DROPTABLE
[junit] POSTHOOK: Input: default@testhivedrivertable
[junit] POSTHOOK: Output: default@testhivedrivertable
[junit] OK
[junit] Hive history 
file=
[junit] PREHOOK: query: drop table testhivedrivertable
[junit] PREHOOK: type: DROPTABLE
[junit] POSTHOOK: query: drop table testhivedrivertable
[junit] POSTHOOK: type: DROPTABLE
[junit] OK
[junit] PREHOOK: query: create table testhivedrivertable (num int)
[junit] PREHOOK: type: DROPTABLE
[junit] POSTHOOK: query: create table testhivedrivertable (num int)
[junit] POSTHOOK: type: DROPTABLE
[junit] POSTHOOK: Output: default@testhivedrivertable
[junit] OK
[junit] Copying file: 

[junit] PREHOOK: query: load data local inpath 
'
 into table testhivedrivertable
[junit] PREHOOK: type: DROPTABLE
[junit] PREHOOK: Output: default@testhivedrivertable
[junit] Copying data from 

[junit] Loading data to table default.testhivedrivertable
[junit] POSTHOOK: query: load data local inpath 
'
 into table testhivedrivertable
[junit] POSTHOOK: type: DROPTABLE
[junit] POSTHOOK: Output: default@testhivedrivertable
[junit] OK
[junit] PREHOOK: query: select * from testhivedrivertable limit 10
[junit] PREHOOK: type: DROPTABLE
[junit] PREHOOK: Input: default@testhivedrivertable
[junit] PREHOOK: Output: 
file:/tmp/hudson/hive_2012-10-26_14-56-02_279_9056377461263601363/-mr-1
[junit] POSTHOOK: query: select * from testhivedrivertable limit 10
[junit] POSTHOOK: type: DROPTABLE
[junit] POSTHOOK: Input: default@testhivedrivertable
[junit] POSTHOOK: Output: 
file:/tmp/hudson/hive_2012-10-26_14-56-02_279_9056377461263601363/-mr-1
[junit] OK
[junit] PREHOOK: query: drop table testhivedrivertable
[junit] PREHOOK: type: DROPTABLE
[junit] PREHOOK: Input: default@testhivedrivertable
[junit] PREHOOK: Output: default@testhivedrivertable
[junit] POSTHOOK: query: drop table testhivedrivertable
[junit] POSTHOOK: type: DROPTABLE
[junit] POSTHOOK: Input: default@testhivedrivertable
[junit] POSTHOOK: Output: default@testhivedrivertable
[junit] OK
[junit] Hive history 
file=
[junit] PREHOOK: query: drop table testhivedrivertable
[junit] PREHOOK: type: DROPTABLE
[junit] POSTHOOK: query: drop table testhivedrivertable
[junit] POSTHOOK: type: DROPTABLE
[junit] OK
[junit] PREHOOK: query: create table testhivedrivertable (num int)
[junit] PREHOOK: type: DROPTABLE
[junit] POSTHOOK: query: create table testhivedrivertable (num int)
[junit] POSTHOOK: type: DROPTABLE
[junit] POSTHOOK: Output: default@testhivedrivertable
[junit] OK
[junit] PREHOOK: query: drop table testhivedrivertable
[junit] PREHOOK: type: DROPTABLE
[junit] PREHOOK: Input: default@testhivedrivertable
[junit] PREHOOK: Output: default@testhivedrivertable
[junit] POSTHOOK: query: drop table testhivedrivertable
[junit] POSTHOOK: type: DROPTABLE
[junit] POSTHOOK: Input: default@testhivedrivertable
[junit] POSTHOOK: Output: default@testhivedrivertable
[junit] OK
[junit] Hive history 
file=
[junit] Hive history 
file=
[junit] Copying file: 

[junit] PREHOOK: query: drop table testhivedrivert

[jira] [Commented] (HIVE-3616) Use Paths consistently

[Thejas M Nair (JIRA)]

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

Thejas M Nair commented on HIVE-3616:
-

I am not actively working on this at the moment, so anybody can feel free to 
take this up.


> Use Paths consistently
> --
>
> Key: HIVE-3616
> URL: https://issues.apache.org/jira/browse/HIVE-3616
> Project: Hive
>  Issue Type: New Feature
>  Components: Diagnosability
>Reporter: Ashutosh Chauhan
> Attachments: HIVE-3616.incomplete.patch
>
>
> Currently, we interchangeably use Path, Uri and Strings in various parts of 
> codebases. This may results in subtle bugs. We should consistently use Path 
> in the codebase. 

--
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-3616) Use Paths consistently

[Thejas M Nair (JIRA)]

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

Thejas M Nair updated HIVE-3616:


Attachment: HIVE-3616.incomplete.patch

Attaching an incomplete patch, needs some work to make it apply on trunk.

> Use Paths consistently
> --
>
> Key: HIVE-3616
> URL: https://issues.apache.org/jira/browse/HIVE-3616
> Project: Hive
>  Issue Type: New Feature
>  Components: Diagnosability
>Reporter: Ashutosh Chauhan
> Attachments: HIVE-3616.incomplete.patch
>
>
> Currently, we interchangeably use Path, Uri and Strings in various parts of 
> codebases. This may results in subtle bugs. We should consistently use Path 
> in the codebase. 

--
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-3625) Statement.updateQuery() returns Method Not Supported exception

[Alex Piyevsky (JIRA)]

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

Alex Piyevsky updated HIVE-3625:


Description: 
I have previously reported the same issue for Hive 0.8.0 in case HIVE-2967.  We 
have now installed 0.9.0 and the same issue still occurs. I found a similar 
issue reported in case HIVE-1450, however the patch uploaded there does not 
seem to be built into the new version. 


  was:
I have previously reported the same issue for Hive 0.8.0 in case HIVE-2967.  We 
have now installed 0.9.0 and the same issue still occurs. 



> Statement.updateQuery() returns Method Not Supported exception
> --
>
> Key: HIVE-3625
> URL: https://issues.apache.org/jira/browse/HIVE-3625
> Project: Hive
>  Issue Type: Bug
>  Components: JDBC
>Affects Versions: 0.9.0
>Reporter: Alex Piyevsky
>  Labels: Hive, JDBC, executeUpdate, statement
>
> I have previously reported the same issue for Hive 0.8.0 in case HIVE-2967.  
> We have now installed 0.9.0 and the same issue still occurs. I found a 
> similar issue reported in case HIVE-1450, however the patch uploaded there 
> does not seem to be built into the new version. 

--
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-3625) Statement.updateQuery() returns Method Not Supported exception

[Alex Piyevsky (JIRA)]

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

Alex Piyevsky updated HIVE-3625:


Labels: Hive JDBC executeUpdate statement  (was: Hive JDBC UpdateQ 
statement)

> Statement.updateQuery() returns Method Not Supported exception
> --
>
> Key: HIVE-3625
> URL: https://issues.apache.org/jira/browse/HIVE-3625
> Project: Hive
>  Issue Type: Bug
>  Components: JDBC
>Affects Versions: 0.9.0
>Reporter: Alex Piyevsky
>  Labels: Hive, JDBC, executeUpdate, statement
>
> I have previously reported the same issue for Hive 0.8.0 in case HIVE-2967.  
> We have now installed 0.9.0 and the same issue still occurs. 

--
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-3625) Statement.updateQuery() returns Method Not Supported exception

[Alex Piyevsky (JIRA)]

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

Alex Piyevsky updated HIVE-3625:


Labels: Hive JDBC UpdateQ statement  (was: )

> Statement.updateQuery() returns Method Not Supported exception
> --
>
> Key: HIVE-3625
> URL: https://issues.apache.org/jira/browse/HIVE-3625
> Project: Hive
>  Issue Type: Bug
>  Components: JDBC
>Affects Versions: 0.9.0
>Reporter: Alex Piyevsky
>  Labels: Hive, JDBC, UpdateQ, statement
>
> I have previously reported the same issue for Hive 0.8.0 in case HIVE-2967.  
> We have now installed 0.9.0 and the same issue still occurs. 

--
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-3625) Statement.updateQuery() returns Method Not Supported exception

[Alex Piyevsky (JIRA)]

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

Alex Piyevsky updated HIVE-3625:


Description: 
I have previously reported the same issue for Hive 0.8.0 in case HIVE-2967.  We 
have now installed 0.9.0 and the same issue still occurs. 


  was:
I have previously reported the same issue for Hive 0.8.0 in case HIVE-2967



> Statement.updateQuery() returns Method Not Supported exception
> --
>
> Key: HIVE-3625
> URL: https://issues.apache.org/jira/browse/HIVE-3625
> Project: Hive
>  Issue Type: Bug
>  Components: JDBC
>Affects Versions: 0.9.0
>Reporter: Alex Piyevsky
>
> I have previously reported the same issue for Hive 0.8.0 in case HIVE-2967.  
> We have now installed 0.9.0 and the same issue still occurs. 

--
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-3625) Statement.updateQuery() returns Method Not Supported exception

[Alex Piyevsky (JIRA)]

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

Alex Piyevsky updated HIVE-3625:


Description: 
I have previously reported the same issue for Hive 0.8.0 in case HIVE-2967


> Statement.updateQuery() returns Method Not Supported exception
> --
>
> Key: HIVE-3625
> URL: https://issues.apache.org/jira/browse/HIVE-3625
> Project: Hive
>  Issue Type: Bug
>  Components: JDBC
>Affects Versions: 0.9.0
>Reporter: Alex Piyevsky
>
> I have previously reported the same issue for Hive 0.8.0 in case HIVE-2967

--
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-3625) Statement.updateQuery() returns Method Not Supported exception

[Alex Piyevsky (JIRA)]

Alex Piyevsky created HIVE-3625:
---

 Summary: Statement.updateQuery() returns Method Not Supported 
exception
 Key: HIVE-3625
 URL: https://issues.apache.org/jira/browse/HIVE-3625
 Project: Hive
  Issue Type: Bug
  Components: JDBC
Affects Versions: 0.9.0
Reporter: Alex Piyevsky




--
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-2693) Add DECIMAL data type

[Vikram Dixit K (JIRA)]

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

Vikram Dixit K commented on HIVE-2693:
--

Yes. For the test however, I am running ant test -Dtestcase=TestCliDriver 
-Dqfile=decimal_1.q. However, I see this error even when I run ant test 
-Dtestcase=TestCliDriver. I ran the compilation step after cleaning up my m2 
and ivy caches.

> Add DECIMAL data type
> -
>
> Key: HIVE-2693
> URL: https://issues.apache.org/jira/browse/HIVE-2693
> Project: Hive
>  Issue Type: New Feature
>  Components: Query Processor, Types
>Reporter: Carl Steinbach
>Assignee: Prasad Mujumdar
> Attachments: HIVE-2693-all.patch, HIVE-2693-fix.patch, 
> HIVE-2693.patch, HIVE-2693-take3.patch
>
>
> Add support for the DECIMAL data type. HIVE-2272 (TIMESTAMP) provides a nice 
> template for how to do this.

--
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-975) Hive ODBC driver for Windows

[Roger Meier (JIRA)]

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

Roger Meier commented on HIVE-975:
--

THRIFT has lib/csharp/src/Thrift.sln which creates 
lib/csharp/src/bin/Debug/Thrift.dll




> Hive ODBC driver for Windows
> 
>
> Key: HIVE-975
> URL: https://issues.apache.org/jira/browse/HIVE-975
> Project: Hive
>  Issue Type: New Feature
>  Components: Clients
> Environment: Windows
>Reporter: Carl Steinbach
>Assignee: Prasad Mujumdar
>
> The current Hive ODBC driver (HIVE-187) is limited to *NIX systems. We need 
> to provide an ODBC driver that is compatible with Windows and the Windows 
> ODBC driver manager.
> It appears that it may be possible to build the current unixODBC driver on 
> Windows:
> http://mailman.unixodbc.org/pipermail/unixodbc-support/2008-June/001779.html
> The other blocker is THRIFT-591: Windows compatible Thrift C++ runtime.

--
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-2693) Add DECIMAL data type

[Josh Wills (JIRA)]

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

Josh Wills commented on HIVE-2693:
--

Hrm, I'm not seeing that. I'm just doing 'ant package' followed by 'ant test'-- 
I assume you're doing the same?

> Add DECIMAL data type
> -
>
> Key: HIVE-2693
> URL: https://issues.apache.org/jira/browse/HIVE-2693
> Project: Hive
>  Issue Type: New Feature
>  Components: Query Processor, Types
>Reporter: Carl Steinbach
>Assignee: Prasad Mujumdar
> Attachments: HIVE-2693-all.patch, HIVE-2693-fix.patch, 
> HIVE-2693.patch, HIVE-2693-take3.patch
>
>
> Add support for the DECIMAL data type. HIVE-2272 (TIMESTAMP) provides a nice 
> template for how to do this.

--
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-2693) Add DECIMAL data type

[Vikram Dixit K (JIRA)]

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

Vikram Dixit K commented on HIVE-2693:
--

I tried the latest patch and it builds successfully. However, I cannot run any 
tests because there seems to be something broken in the parser. Posting the 
error below:

[junit] FAILED: ParseException line 1:23 cannot recognize input near 
''/grid/0/hive/BigD/data/files/kv1.txt'' '(' ''2008-04-08''
[junit] 
[junit] java.lang.Exception: load command: LOAD DATA LOCAL INPATH 
'/grid/0/hive/BigD/data/files/kv1.txt' OVERWRITE INTO TABLE srcpart PARTITION 
(ds='2008-04-08',hr='11') failed with exit code= 4
[junit] at 
org.apache.hadoop.hive.ql.QTestUtil.runLoadCmd(QTestUtil.java:468)
[junit] at 
org.apache.hadoop.hive.ql.QTestUtil.createSources(QTestUtil.java:512)
[junit] at 
org.apache.hadoop.hive.cli.TestCliDriver.(TestCliDriver.java:55)


> Add DECIMAL data type
> -
>
> Key: HIVE-2693
> URL: https://issues.apache.org/jira/browse/HIVE-2693
> Project: Hive
>  Issue Type: New Feature
>  Components: Query Processor, Types
>Reporter: Carl Steinbach
>Assignee: Prasad Mujumdar
> Attachments: HIVE-2693-all.patch, HIVE-2693-fix.patch, 
> HIVE-2693.patch, HIVE-2693-take3.patch
>
>
> Add support for the DECIMAL data type. HIVE-2272 (TIMESTAMP) provides a nice 
> template for how to do this.

--
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-3471) Implement grouping sets in hive

[Ivan Gorbachev (JIRA)]

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

Ivan Gorbachev commented on HIVE-3471:
--

https://reviews.facebook.net/D6219

> Implement grouping sets in hive
> ---
>
> Key: HIVE-3471
> URL: https://issues.apache.org/jira/browse/HIVE-3471
> Project: Hive
>  Issue Type: New Feature
>  Components: Query Processor
>Reporter: Namit Jain
>Assignee: Ivan Gorbachev
> Attachments: jira-3471.0.patch
>
>


--
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-3471) Implement grouping sets in hive

[Ivan Gorbachev (JIRA)]

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

Ivan Gorbachev updated HIVE-3471:
-

Attachment: jira-3471.0.patch

> Implement grouping sets in hive
> ---
>
> Key: HIVE-3471
> URL: https://issues.apache.org/jira/browse/HIVE-3471
> Project: Hive
>  Issue Type: New Feature
>  Components: Query Processor
>Reporter: Namit Jain
>Assignee: Ivan Gorbachev
> Attachments: jira-3471.0.patch
>
>


--
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-3471) Implement grouping sets in hive

[Ivan Gorbachev (JIRA)]

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

Ivan Gorbachev updated HIVE-3471:
-

Status: Patch Available  (was: Open)

> Implement grouping sets in hive
> ---
>
> Key: HIVE-3471
> URL: https://issues.apache.org/jira/browse/HIVE-3471
> Project: Hive
>  Issue Type: New Feature
>  Components: Query Processor
>Reporter: Namit Jain
>Assignee: Ivan Gorbachev
> Attachments: jira-3471.0.patch
>
>


--
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-3524) Storing certain Exception objects thrown in HiveMetaStore.java in MetaStoreEndFunctionContext

[Kevin Wilfong (JIRA)]

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

Kevin Wilfong commented on HIVE-3524:
-

+1

> Storing certain Exception objects thrown in HiveMetaStore.java in 
> MetaStoreEndFunctionContext
> -
>
> Key: HIVE-3524
> URL: https://issues.apache.org/jira/browse/HIVE-3524
> Project: Hive
>  Issue Type: Improvement
>  Components: Metastore
>Affects Versions: 0.10.0
>Reporter: Maheshwaran Srinivasan
>Assignee: Maheshwaran Srinivasan
>Priority: Minor
> Fix For: 0.10.0
>
> Attachments: HIVE-3524.1.patch.txt, HIVE-3524.2.patch.txt, 
> HIVE-3524.3.patch.txt
>
>   Original Estimate: 168h
>  Remaining Estimate: 168h
>
> Idea is to store exception objects thrown in the scope of the public 
> functions of HiveMetaStore.java. Exception objects will be stored in 
> MetaStoreEndFunctionContext. These could then be optionally processed to 
> gather interesting statistics.

--
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-3610) Add a command "Explain dependency ..."

[Kevin Wilfong (JIRA)]

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

Kevin Wilfong commented on HIVE-3610:
-

A minor comment on the diff, otherwise looks good.

> Add a command "Explain dependency ..."
> --
>
> Key: HIVE-3610
> URL: https://issues.apache.org/jira/browse/HIVE-3610
> Project: Hive
>  Issue Type: New Feature
>  Components: Query Processor
>Affects Versions: 0.9.0
>Reporter: Sambavi Muthukrishnan
>Assignee: Sambavi Muthukrishnan
>Priority: Minor
> Attachments: explain_dependency.1.patch
>
>
> Add a new command "EXPLAIN DEPENDENCY".
> Any query can be passed to EXPLAIN DEPENDENCY as with EXPLAIN 
> (FORMATTED/EXTENDED). The output of this command will be JSON that provides 
> the list of tables and partitions that the query depends on.
> One possible use case is to determine the set of tables/views that are used 
> by a view, and the set of partitions that are used by a given query on that 
> view. This will allow a view to be replicated from one Hive instance to 
> another, since we can determine the set of objects that need to be replicated 
> for replication of the view to be successful.
> Example output:
> {"input_tables":[{"tablename": "default@test_sambavi_v2", "tabletype": 
> "EXTERNAL_TABLE"}, {"tablename": "default@test_sambavi_v1", "tabletype": 
> "TABLE"}], "input 
> partitions":["default@srcpart@ds=2008-04-08/hr=11","default@srcpart@ds=2008-04-08/hr=12"]}

--
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-3596) Regression - HiveConf static variable causes issues in long running JVM instances with /tmp/ data

[Chris McConnell (JIRA)]

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

Chris McConnell commented on HIVE-3596:
---

Good catch Carl -- I believe when I tested my rm of the data files required 
confirmation and perhaps I did not say "yes." 

Deeper digging the issue, will update when I have a clear option. 

> Regression - HiveConf static variable causes issues in long running JVM 
> instances with /tmp/ data
> -
>
> Key: HIVE-3596
> URL: https://issues.apache.org/jira/browse/HIVE-3596
> Project: Hive
>  Issue Type: Bug
>  Components: Configuration
>Affects Versions: 0.8.0, 0.8.1, 0.9.0
>Reporter: Chris McConnell
>Assignee: Chris McConnell
> Fix For: 0.8.1, 0.9.0, 0.10.0
>
> Attachments: HIVE-3596.patch
>
>
> With Hive 0.8.x, HiveConf was changed to utilize the private, static member 
> "confVarURL" which points to /tmp/hive--.xml for job 
> configuration settings. 
> During long running JVMs, such as a Beeswax server, which creates multiple 
> HiveConf objects over time this variable does not properly get updated 
> between jobs and can cause job failure if the OS cleans /tmp/ during a cron 
> job. 

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

Build failed in Jenkins: Hive-0.9.1-SNAPSHOT-h0.21-keepgoing=false #179

[Apache Jenkins Server]

See 


--
[...truncated 5562 lines...]
[ivy:resolve]   [SUCCESSFUL ] 
org.apache.hadoop#hadoop-test;0.20.2!hadoop-test.jar (267ms)
[ivy:resolve] downloading 
http://repo1.maven.org/maven2/commons-cli/commons-cli/1.2/commons-cli-1.2.jar 
...
[ivy:resolve]  (40kB)
[ivy:resolve] .. (0kB)
[ivy:resolve]   [SUCCESSFUL ] commons-cli#commons-cli;1.2!commons-cli.jar 
(129ms)
[ivy:resolve] downloading 
http://repo1.maven.org/maven2/xmlenc/xmlenc/0.52/xmlenc-0.52.jar ...
[ivy:resolve] .. (14kB)
[ivy:resolve] .. (0kB)
[ivy:resolve]   [SUCCESSFUL ] xmlenc#xmlenc;0.52!xmlenc.jar (341ms)
[ivy:resolve] downloading 
http://repo1.maven.org/maven2/commons-httpclient/commons-httpclient/3.0.1/commons-httpclient-3.0.1.jar
 ...
[ivy:resolve] . (273kB)
[ivy:resolve] .. (0kB)
[ivy:resolve]   [SUCCESSFUL ] 
commons-httpclient#commons-httpclient;3.0.1!commons-httpclient.jar (137ms)
[ivy:resolve] downloading 
http://repo1.maven.org/maven2/commons-codec/commons-codec/1.3/commons-codec-1.3.jar
 ...
[ivy:resolve] . (45kB)
[ivy:resolve] .. (0kB)
[ivy:resolve]   [SUCCESSFUL ] commons-codec#commons-codec;1.3!commons-codec.jar 
(414ms)
[ivy:resolve] downloading 
http://repo1.maven.org/maven2/commons-net/commons-net/1.4.1/commons-net-1.4.1.jar
 ...
[ivy:resolve]  (176kB)
[ivy:resolve] .. (0kB)
[ivy:resolve]   [SUCCESSFUL ] commons-net#commons-net;1.4.1!commons-net.jar 
(145ms)
[ivy:resolve] downloading 
http://repo1.maven.org/maven2/org/mortbay/jetty/jetty/6.1.14/jetty-6.1.14.jar 
...
[ivy:resolve] .. (504kB)
[ivy:resolve] .. (0kB)
[ivy:resolve]   [SUCCESSFUL ] org.mortbay.jetty#jetty;6.1.14!jetty.jar (217ms)
[ivy:resolve] downloading 
http://repo1.maven.org/maven2/org/mortbay/jetty/jetty-util/6.1.14/jetty-util-6.1.14.jar
 ...
[ivy:resolve]  (159kB)
[ivy:resolve] .. (0kB)
[ivy:resolve]   [SUCCESSFUL ] 
org.mortbay.jetty#jetty-util;6.1.14!jetty-util.jar (138ms)
[ivy:resolve] downloading 
http://repo1.maven.org/maven2/tomcat/jasper-runtime/5.5.12/jasper-runtime-5.5.12.jar
 ...
[ivy:resolve]  (74kB)
[ivy:resolve] .. (0kB)
[ivy:resolve]   [SUCCESSFUL ] tomcat#jasper-runtime;5.5.12!jasper-runtime.jar 
(143ms)
[ivy:resolve] downloading 
http://repo1.maven.org/maven2/tomcat/jasper-compiler/5.5.12/jasper-compiler-5.5.12.jar
 ...
[ivy:resolve]  (395kB)
[ivy:resolve] .. (0kB)
[ivy:resolve]   [SUCCESSFUL ] tomcat#jasper-compiler;5.5.12!jasper-compiler.jar 
(275ms)
[ivy:resolve] downloading 
http://repo1.maven.org/maven2/org/mortbay/jetty/jsp-api-2.1/6.1.14/jsp-api-2.1-6.1.14.jar
 ...
[ivy:resolve] .. (131kB)
[ivy:resolve] .. (0kB)
[ivy:resolve]   [SUCCESSFUL ] 
org.mortbay.jetty#jsp-api-2.1;6.1.14!jsp-api-2.1.jar (304ms)
[ivy:resolve] downloading 
http://repo1.maven.org/maven2/org/mortbay/jetty/jsp-2.1/6.1.14/jsp-2.1-6.1.14.jar
 ...
[ivy:resolve] 

 (1000kB)
[ivy:resolve] .. (0kB)
[ivy:resolve]   [SUCCESSFUL ] org.mortbay.jetty#jsp-2.1;6.1.14!jsp-2.1.jar 
(677ms)
[ivy:resolve] downloading 
http://repo1.maven.org/maven2/commons-el/commons-el/1.0/commons-el-1.0.jar ...
[ivy:resolve] ... (109kB)
[ivy:resolve] .. (0kB)
[ivy:resolve]   [SUCCESSFUL ] commons-el#commons-el;1.0!commons-el.jar (107ms)
[ivy:resolve] downloading 
http://repo1.maven.org/maven2/net/java/dev/jets3t/jets3t/0.7.1/jets3t-0.7.1.jar 
...
[ivy:resolve] . (368kB)
[ivy:resolve] .. (0kB)
[ivy:resolve]   [SUCCESSFUL ] net.java.dev.jets3t#jets3t;0.7.1!jets3t.jar 
(291ms)
[ivy:resolve] downloading 
http://repo1.maven.org/maven2/org/mortbay/jetty/servlet-api-2.5/6.1.14/servlet-api-2.5-6.1.14.jar
 ...
[ivy:resolve] ... (129kB)
[ivy:resolve] .. (0kB)
[ivy:resolve]   [SUCCESSFUL ] 
org.mortbay.jetty#servlet-api-2.5;6.1.14!servlet-api-2.5.jar (109ms)
[ivy:resolve] downloading 
http://repo1.maven.org/maven2/net/sf/kosmosfs/kfs/0.3/kfs-0.3.jar ...
[ivy:resolve] .. (11kB)
[ivy:resolve] .. (0kB)
[ivy:resolve]   [SUCCESSFUL ] net.sf.kosmosfs#kfs;0.3!kfs.jar (163ms)
[ivy:resolve] downloading 
http://repo1.maven.org/maven2/junit/junit/4.5/junit-4.5.jar ...
[ivy:resolve] . (194kB)
[ivy:resolve] .. (0kB)
[ivy:resolve]   [SUCCESSFUL ] junit#junit;4.5!junit.jar (182ms)
[ivy:resolve] downloading 
http://repo1.maven.org/maven2/hsqldb/hsqldb/1.8.0.10/hsqldb-1.8.0.10.jar ...
[ivy:resolve] 
... 
(690kB)
[ivy:resolve] .. (0kB)
[ivy:resolve]   [SUCCESSFUL ] hsqldb#hsqldb;1.8.0.10!hsqldb.jar (2842ms)
[ivy:resolve] downloading 
http://repo1.maven.org/maven2/oro/oro/2.0.8/oro-2.0.8.jar ...
[ivy:resolve] .. (63kB)
[ivy:resolve] .. (0kB)
[

Hive-trunk-h0.21 - Build # 1759 - Still Failing

[Apache Jenkins Server]

Changes for Build #1747

Changes for Build #1748
[namit] HIVE-3544 union involving double column with a map join subquery will 
fail or give wrong results
(Kevin Wilfong via namit)

[cws] HIVE-3590. TCP KeepAlive and connection timeout for the HiveServer 
(Esteban Gutierrez via cws)


Changes for Build #1749

Changes for Build #1750
[ecapriolo] HIVE-3599 missing return of compression codec to pool (Owen 
O'Malley via egc)


Changes for Build #1751

Changes for Build #1752

Changes for Build #1753

Changes for Build #1754

Changes for Build #1755
[kevinwilfong] HIVE-3152. Disallow certain character patterns in partition 
names. (Ivan Gorbachev via kevinwilfong)


Changes for Build #1756
[hashutosh] HIVE-3519 : partition to directory comparison in 
CombineHiveInputFormat needs to accept partitions dir without scheme (Thejas 
Nair via Ashutosh Chauhan)


Changes for Build #1757

Changes for Build #1758
[kevinwilfong] HIVE-3433. Implement CUBE and ROLLUP operators in Hive. (Ivan 
Gorbachev and Namit Jain via kevinwilfong)


Changes for Build #1759



No tests ran.

The Apache Jenkins build system has built Hive-trunk-h0.21 (build #1759)

Status: Still Failing

Check console output at https://builds.apache.org/job/Hive-trunk-h0.21/1759/ to 
view the results.

[jira] [Updated] (HIVE-3624) Unable to add single file partition

[Hans Uhlig (JIRA)]

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

Hans Uhlig updated HIVE-3624:
-

Component/s: (was: StorageHandler)
 Metastore

> Unable to add single file partition
> ---
>
> Key: HIVE-3624
> URL: https://issues.apache.org/jira/browse/HIVE-3624
> Project: Hive
>  Issue Type: Bug
>  Components: Metastore
>Affects Versions: 0.9.0
> Environment: ubuntu, centos
>Reporter: Hans Uhlig
>
> Hive complains when calling ALTER TABLE ADD PARTITION on an EXTERNAL table 
> when the partition location points to a single file. This is caused during 
> Warehouse.mkdirs called by 
> org.apache.hadoop.hive.metastore.HiveMetaStore$HMSHandler.add_partition_core_notxn(HiveMetaStore.java:1494).
>  The external data already exists in place and shouldnt need additional 
> directories needed.

--
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-3624) Unable to add single file partition

[Hans Uhlig (JIRA)]

Hans Uhlig created HIVE-3624:


 Summary: Unable to add single file partition
 Key: HIVE-3624
 URL: https://issues.apache.org/jira/browse/HIVE-3624
 Project: Hive
  Issue Type: Bug
  Components: StorageHandler
Affects Versions: 0.9.0
 Environment: ubuntu, centos
Reporter: Hans Uhlig


Hive complains when calling ALTER TABLE ADD PARTITION on an EXTERNAL table when 
the partition location points to a single file. This is caused during 
Warehouse.mkdirs called by 
org.apache.hadoop.hive.metastore.HiveMetaStore$HMSHandler.add_partition_core_notxn(HiveMetaStore.java:1494).
 The external data already exists in place and shouldnt need additional 
directories needed.

--
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-3623) Reset operator-id before executing parse tests

[Navis (JIRA)]

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

Navis updated HIVE-3623:


Status: Patch Available  (was: Open)

> Reset operator-id before executing parse tests
> --
>
> Key: HIVE-3623
> URL: https://issues.apache.org/jira/browse/HIVE-3623
> Project: Hive
>  Issue Type: Improvement
>  Components: Tests
>Reporter: Navis
>Assignee: Navis
>Priority: Trivial
> Attachments: HIVE-3623.D6213.1.patch
>
>
> Parse test in hive-exec outputs XML file containing operator ids, which can 
> be vary by previous query history. Resetting it 0 before each test could make 
> test result independent to history.

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

Hive-trunk-h0.21 - Build # 1758 - Still Failing

[Apache Jenkins Server]

Changes for Build #1747

Changes for Build #1748
[namit] HIVE-3544 union involving double column with a map join subquery will 
fail or give wrong results
(Kevin Wilfong via namit)

[cws] HIVE-3590. TCP KeepAlive and connection timeout for the HiveServer 
(Esteban Gutierrez via cws)


Changes for Build #1749

Changes for Build #1750
[ecapriolo] HIVE-3599 missing return of compression codec to pool (Owen 
O'Malley via egc)


Changes for Build #1751

Changes for Build #1752

Changes for Build #1753

Changes for Build #1754

Changes for Build #1755
[kevinwilfong] HIVE-3152. Disallow certain character patterns in partition 
names. (Ivan Gorbachev via kevinwilfong)


Changes for Build #1756
[hashutosh] HIVE-3519 : partition to directory comparison in 
CombineHiveInputFormat needs to accept partitions dir without scheme (Thejas 
Nair via Ashutosh Chauhan)


Changes for Build #1757

Changes for Build #1758
[kevinwilfong] HIVE-3433. Implement CUBE and ROLLUP operators in Hive. (Ivan 
Gorbachev and Namit Jain via kevinwilfong)




2 tests failed.
REGRESSION:  
org.apache.hadoop.hive.cli.TestNegativeCliDriver.testNegativeCliDriver_script_broken_pipe1

Error Message:
Unexpected exception See build/ql/tmp/hive.log, or try "ant test ... 
-Dtest.silent=false" to get more logs.

Stack Trace:
junit.framework.AssertionFailedError: Unexpected exception
See build/ql/tmp/hive.log, or try "ant test ... -Dtest.silent=false" to get 
more logs.
at junit.framework.Assert.fail(Assert.java:47)
at 
org.apache.hadoop.hive.cli.TestNegativeCliDriver.testNegativeCliDriver_script_broken_pipe1(TestNegativeCliDriver.java:11553)
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 junit.framework.TestCase.runTest(TestCase.java:168)
at junit.framework.TestCase.runBare(TestCase.java:134)
at junit.framework.TestResult$1.protect(TestResult.java:110)
at junit.framework.TestResult.runProtected(TestResult.java:128)
at junit.framework.TestResult.run(TestResult.java:113)
at junit.framework.TestCase.run(TestCase.java:124)
at junit.framework.TestSuite.runTest(TestSuite.java:232)
at junit.framework.TestSuite.run(TestSuite.java:227)
at 
org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:422)
at 
org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.launch(JUnitTestRunner.java:931)
at 
org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.main(JUnitTestRunner.java:785)


FAILED:  org.apache.hadoop.hive.ql.parse.TestParse.testParse_union

Error Message:
Unexpected exception See build/ql/tmp/hive.log, or try "ant test ... 
-Dtest.silent=false" to get more logs.

Stack Trace:
junit.framework.AssertionFailedError: Unexpected exception
See build/ql/tmp/hive.log, or try "ant test ... -Dtest.silent=false" to get 
more logs.
at junit.framework.Assert.fail(Assert.java:47)
at 
org.apache.hadoop.hive.ql.parse.TestParse.testParse_union(TestParse.java:1618)
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 junit.framework.TestCase.runTest(TestCase.java:168)
at junit.framework.TestCase.runBare(TestCase.java:134)
at junit.framework.TestResult$1.protect(TestResult.java:110)
at junit.framework.TestResult.runProtected(TestResult.java:128)
at junit.framework.TestResult.run(TestResult.java:113)
at junit.framework.TestCase.run(TestCase.java:124)
at junit.framework.TestSuite.runTest(TestSuite.java:232)
at junit.framework.TestSuite.run(TestSuite.java:227)
at 
org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:422)
at 
org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.launch(JUnitTestRunner.java:931)
at 
org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.main(JUnitTestRunner.java:785)




The Apache Jenkins build system has built Hive-trunk-h0.21 (build #1758)

Status: Still Failing

Check console output at https://builds.apache.org/job/Hive-trunk-h0.21/1758/ to 
view the results.

[jira] [Commented] (HIVE-3433) Implement CUBE and ROLLUP operators in Hive

[Hudson (JIRA)]

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

Hudson commented on HIVE-3433:
--

Integrated in Hive-trunk-h0.21 #1758 (See 
[https://builds.apache.org/job/Hive-trunk-h0.21/1758/])
HIVE-3433. Implement CUBE and ROLLUP operators in Hive. (Ivan Gorbachev and 
Namit Jain via kevinwilfong) (Revision 1402245)

 Result = FAILURE
kevinwilfong : 
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1402245
Files : 
* /hive/trunk/eclipse-templates/.classpath
* /hive/trunk/ivy/libraries.properties
* /hive/trunk/ql/build.xml
* /hive/trunk/ql/ivy.xml
* /hive/trunk/ql/src/java/org/apache/hadoop/hive/ql/ErrorMsg.java
* /hive/trunk/ql/src/java/org/apache/hadoop/hive/ql/exec/GroupByOperator.java
* /hive/trunk/ql/src/java/org/apache/hadoop/hive/ql/parse/Hive.g
* /hive/trunk/ql/src/java/org/apache/hadoop/hive/ql/parse/QBParseInfo.java
* /hive/trunk/ql/src/java/org/apache/hadoop/hive/ql/parse/SemanticAnalyzer.java
* /hive/trunk/ql/src/java/org/apache/hadoop/hive/ql/plan/GroupByDesc.java
* /hive/trunk/ql/src/test/queries/clientnegative/groupby_cube1.q
* /hive/trunk/ql/src/test/queries/clientnegative/groupby_cube2.q
* /hive/trunk/ql/src/test/queries/clientnegative/groupby_rollup1.q
* /hive/trunk/ql/src/test/queries/clientnegative/groupby_rollup2.q
* /hive/trunk/ql/src/test/queries/clientpositive/groupby_cube1.q
* /hive/trunk/ql/src/test/queries/clientpositive/groupby_rollup1.q
* /hive/trunk/ql/src/test/results/clientnegative/groupby_cube1.q.out
* /hive/trunk/ql/src/test/results/clientnegative/groupby_cube2.q.out
* /hive/trunk/ql/src/test/results/clientnegative/groupby_rollup1.q.out
* /hive/trunk/ql/src/test/results/clientnegative/groupby_rollup2.q.out
* /hive/trunk/ql/src/test/results/clientpositive/groupby_cube1.q.out
* /hive/trunk/ql/src/test/results/clientpositive/groupby_rollup1.q.out
* /hive/trunk/ql/src/test/results/compiler/plan/groupby1.q.xml
* /hive/trunk/ql/src/test/results/compiler/plan/groupby2.q.xml
* /hive/trunk/ql/src/test/results/compiler/plan/groupby3.q.xml
* /hive/trunk/ql/src/test/results/compiler/plan/groupby4.q.xml
* /hive/trunk/ql/src/test/results/compiler/plan/groupby5.q.xml
* /hive/trunk/ql/src/test/results/compiler/plan/groupby6.q.xml


> Implement CUBE and ROLLUP operators in Hive
> ---
>
> Key: HIVE-3433
> URL: https://issues.apache.org/jira/browse/HIVE-3433
> Project: Hive
>  Issue Type: New Feature
>  Components: Query Processor
>Affects Versions: 0.10.0
>Reporter: Sambavi Muthukrishnan
>Assignee: Namit Jain
> Fix For: 0.10.0
>
> Attachments: hive.3433.1.patch, hive.3433.2.patch, hive.3433.3.patch, 
> hive-3433.4.patch, hive-3433.5.patch, hive-3433.6.patch
>
>


--
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-3623) Reset operator-id before executing parse tests

[Phabricator (JIRA)]

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

Phabricator updated HIVE-3623:
--

Attachment: HIVE-3623.D6213.1.patch

navis requested code review of "HIVE-3623 [jira] Reset operator-id before 
executing parse tests".
Reviewers: JIRA

  DPAL-1925 Reset operator-id before executing parse tests

  Parse test in hive-exec outputs XML file containing operator ids, which can 
be vary by previous query history. Resetting it 0 before each test could make 
test result independent to history.

TEST PLAN
  EMPTY

REVISION DETAIL
  https://reviews.facebook.net/D6213

AFFECTED FILES
  ql/src/test/results/compiler/plan/cast1.q.xml
  ql/src/test/results/compiler/plan/groupby1.q.xml
  ql/src/test/results/compiler/plan/groupby2.q.xml
  ql/src/test/results/compiler/plan/groupby3.q.xml
  ql/src/test/results/compiler/plan/groupby4.q.xml
  ql/src/test/results/compiler/plan/groupby5.q.xml
  ql/src/test/results/compiler/plan/groupby6.q.xml
  ql/src/test/results/compiler/plan/input1.q.xml
  ql/src/test/results/compiler/plan/input2.q.xml
  ql/src/test/results/compiler/plan/input20.q.xml
  ql/src/test/results/compiler/plan/input3.q.xml
  ql/src/test/results/compiler/plan/input4.q.xml
  ql/src/test/results/compiler/plan/input5.q.xml
  ql/src/test/results/compiler/plan/input6.q.xml
  ql/src/test/results/compiler/plan/input7.q.xml
  ql/src/test/results/compiler/plan/input8.q.xml
  ql/src/test/results/compiler/plan/input9.q.xml
  ql/src/test/results/compiler/plan/input_part1.q.xml
  ql/src/test/results/compiler/plan/input_testsequencefile.q.xml
  ql/src/test/results/compiler/plan/input_testxpath.q.xml
  ql/src/test/results/compiler/plan/input_testxpath2.q.xml
  ql/src/test/results/compiler/plan/join1.q.xml
  ql/src/test/results/compiler/plan/join2.q.xml
  ql/src/test/results/compiler/plan/join3.q.xml
  ql/src/test/results/compiler/plan/join4.q.xml
  ql/src/test/results/compiler/plan/join5.q.xml
  ql/src/test/results/compiler/plan/join6.q.xml
  ql/src/test/results/compiler/plan/join7.q.xml
  ql/src/test/results/compiler/plan/join8.q.xml
  ql/src/test/results/compiler/plan/sample1.q.xml
  ql/src/test/results/compiler/plan/sample2.q.xml
  ql/src/test/results/compiler/plan/sample3.q.xml
  ql/src/test/results/compiler/plan/sample4.q.xml
  ql/src/test/results/compiler/plan/sample5.q.xml
  ql/src/test/results/compiler/plan/sample6.q.xml
  ql/src/test/results/compiler/plan/sample7.q.xml
  ql/src/test/results/compiler/plan/subq.q.xml
  ql/src/test/results/compiler/plan/udf1.q.xml
  ql/src/test/results/compiler/plan/udf4.q.xml
  ql/src/test/results/compiler/plan/udf6.q.xml
  ql/src/test/results/compiler/plan/udf_case.q.xml
  ql/src/test/results/compiler/plan/udf_when.q.xml
  ql/src/test/templates/TestParse.vm

MANAGE HERALD DIFFERENTIAL RULES
  https://reviews.facebook.net/herald/view/differential/

WHY DID I GET THIS EMAIL?
  https://reviews.facebook.net/herald/transcript/14817/

To: JIRA, navis


> Reset operator-id before executing parse tests
> --
>
> Key: HIVE-3623
> URL: https://issues.apache.org/jira/browse/HIVE-3623
> Project: Hive
>  Issue Type: Improvement
>  Components: Tests
>Reporter: Navis
>Assignee: Navis
>Priority: Trivial
> Attachments: HIVE-3623.D6213.1.patch
>
>
> Parse test in hive-exec outputs XML file containing operator ids, which can 
> be vary by previous query history. Resetting it 0 before each test could make 
> test result independent to history.

--
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-3614) TestParse_Union is failing on trunk

[Navis (JIRA)]

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

Navis commented on HIVE-3614:
-

I've made HIVE-3623 as stated above.

> TestParse_Union is failing on trunk
> ---
>
> Key: HIVE-3614
> URL: https://issues.apache.org/jira/browse/HIVE-3614
> Project: Hive
>  Issue Type: Bug
>  Components: Query Processor
>Affects Versions: 0.10.0
>Reporter: Ashutosh Chauhan
>
> Test is generating output different then expected and thus failing.

--
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-2693) Add DECIMAL data type

[Josh Wills (JIRA)]

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

Josh Wills updated HIVE-2693:
-

Attachment: HIVE-2693-take3.patch

This compiles and makes it to the test phase before I started running into 
errors, but I can't tell if it's a problem w/the patch or my test harness. In 
any case, that's enough work on it for tonight.

> Add DECIMAL data type
> -
>
> Key: HIVE-2693
> URL: https://issues.apache.org/jira/browse/HIVE-2693
> Project: Hive
>  Issue Type: New Feature
>  Components: Query Processor, Types
>Reporter: Carl Steinbach
>Assignee: Prasad Mujumdar
> Attachments: HIVE-2693-all.patch, HIVE-2693-fix.patch, 
> HIVE-2693.patch, HIVE-2693-take3.patch
>
>
> Add support for the DECIMAL data type. HIVE-2272 (TIMESTAMP) provides a nice 
> template for how to do this.

--
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-3623) Reset operator-id before executing parse tests

[Navis (JIRA)]

Navis created HIVE-3623:
---

 Summary: Reset operator-id before executing parse tests
 Key: HIVE-3623
 URL: https://issues.apache.org/jira/browse/HIVE-3623
 Project: Hive
  Issue Type: Improvement
  Components: Tests
Reporter: Navis
Assignee: Navis
Priority: Trivial


Parse test in hive-exec outputs XML file containing operator ids, which can be 
vary by previous query history. Resetting it 0 before each test could make test 
result independent to history.

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