date:20121207

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

2012-12-07 Thread Apache Jenkins Server

Changes for Build #1831
[namit] HIVE-3747 Provide hive operation name for hookContext
(Shreepadma Venugopalan via namit)


Changes for Build #1832

Changes for Build #1833
[namit] HIVE-3750 JDBCStatsPublisher fails when ID length exceeds length of ID 
column
(Kevin Wilfong via namit)


Changes for Build #1835
[namit] HIVE-3073 Hive List Bucketing - DML support
(Gang Tim Liu via namit)

[namit] HIVE-3771 HIVE-3750 broke TestParse
(Kevin Wilfong via namit)

[hashutosh] HIVE-3384 : HIVE JDBC module won't compile under JDK1.7 as new 
methods added in JDBC specification (Shengsheng Huang, Chris Drome, Mikhail 
Bautin via Ashutosh Chauhan)

[namit] HIVE-3702 Renaming table changes table location scheme/authority
(Kevin Wilfong via namit)


Changes for Build #1836
[namit] HIVE-2723 should throw "Ambiguous column reference key" Exception in 
particular
join condition (Navis via namit)

[namit] HIVE-3594 When Group by Partition Column Type is Timestamp or STRING 
Which Format contains "HH:MM:SS",
It will occur URISyntaxException (Navis via namit)


Changes for Build #1837
[namit] HIVE-3762 Minor fix for 'tableName' in Hive.g
(Navis via namit)


Changes for Build #1838

Changes for Build #1839
[namit] HIVE-2477 Use name of original expression for name of CAST output
(Navis via namit)


Changes for Build #1840
[hashutosh] HIVE-3400 : Add Retries to Hive MetaStore Connections (Bhushan 
Mandhani via Ashutosh Chauhan)


Changes for Build #1841
[namit] HIVE-3767 BucketizedHiveInputFormat should be automatically used with 
Bucketized Map Joins also (Gang Tim Liu via namit)


Changes for Build #1842
[namit] HIVE-3140 Comment indenting is broken for "describe" in CLI
(Zhenxiao Luo via namit)




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

Error Message:
Forked Java VM exited abnormally. Please note the time in the report does not 
reflect the time until the VM exit.

Stack Trace:
junit.framework.AssertionFailedError: Forked Java VM exited abnormally. Please 
note the time in the report does not reflect the time until the VM exit.
at 
net.sf.antcontrib.logic.ForTask.doSequentialIteration(ForTask.java:259)
at net.sf.antcontrib.logic.ForTask.doToken(ForTask.java:268)
at net.sf.antcontrib.logic.ForTask.doTheTasks(ForTask.java:324)
at net.sf.antcontrib.logic.ForTask.execute(ForTask.java:244)


FAILED:  org.apache.hadoop.hive.cli.TestCliDriver.testCliDriver_stats19

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.TestCliDriver.testCliDriver_stats19(TestCliDriver.java:41312)
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 #1842)

Status: Still Failing

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

[jira] [Commented] (HIVE-3140) Comment indenting is broken for "describe" in CLI

2012-12-07 Thread Hudson (JIRA)


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

Hudson commented on HIVE-3140:
--

Integrated in Hive-trunk-h0.21 #1842 (See 
[https://builds.apache.org/job/Hive-trunk-h0.21/1842/])
HIVE-3140 Comment indenting is broken for "describe" in CLI
(Zhenxiao Luo via namit) (Revision 1418405)

 Result = FAILURE
namit : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1418405
Files : 
* /hive/trunk/contrib/src/test/results/clientpositive/fileformat_base64.q.out
* /hive/trunk/contrib/src/test/results/clientpositive/serde_s3.q.out
* /hive/trunk/hbase-handler/src/test/results/positive/hbase_queries.q.out
* /hive/trunk/hwi/src/test/org/apache/hadoop/hive/hwi/TestHWISessionManager.java
* /hive/trunk/jdbc/src/test/org/apache/hadoop/hive/jdbc/TestJdbcDriver.java
* /hive/trunk/ql/src/java/org/apache/hadoop/hive/ql/exec/DDLTask.java
* 
/hive/trunk/ql/src/java/org/apache/hadoop/hive/ql/metadata/formatting/MetaDataFormatUtils.java
* 
/hive/trunk/ql/src/java/org/apache/hadoop/hive/ql/metadata/formatting/TextMetaDataFormatter.java
* /hive/trunk/ql/src/test/queries/clientpositive/describe_comment_indent.q
* /hive/trunk/ql/src/test/results/clientnegative/desc_failure2.q.out
* 
/hive/trunk/ql/src/test/results/clientnegative/drop_partition_filter_failure2.q.out
* /hive/trunk/ql/src/test/results/clientnegative/protectmode_part_no_drop.q.out
* /hive/trunk/ql/src/test/results/clientnegative/protectmode_tbl2.q.out
* /hive/trunk/ql/src/test/results/clientnegative/protectmode_tbl3.q.out
* /hive/trunk/ql/src/test/results/clientnegative/protectmode_tbl4.q.out
* /hive/trunk/ql/src/test/results/clientnegative/protectmode_tbl5.q.out
* /hive/trunk/ql/src/test/results/clientnegative/protectmode_tbl_no_drop.q.out
* /hive/trunk/ql/src/test/results/clientnegative/set_hiveconf_validation0.q.out
* /hive/trunk/ql/src/test/results/clientnegative/set_hiveconf_validation1.q.out
* /hive/trunk/ql/src/test/results/clientpositive/alter1.q.out
* /hive/trunk/ql/src/test/results/clientpositive/alter2.q.out
* /hive/trunk/ql/src/test/results/clientpositive/alter3.q.out
* /hive/trunk/ql/src/test/results/clientpositive/alter4.q.out
* /hive/trunk/ql/src/test/results/clientpositive/alter5.q.out
* /hive/trunk/ql/src/test/results/clientpositive/alter_index.q.out
* /hive/trunk/ql/src/test/results/clientpositive/alter_merge_2.q.out
* /hive/trunk/ql/src/test/results/clientpositive/alter_merge_stats.q.out
* 
/hive/trunk/ql/src/test/results/clientpositive/alter_partition_format_loc.q.out
* /hive/trunk/ql/src/test/results/clientpositive/alter_table_serde.q.out
* /hive/trunk/ql/src/test/results/clientpositive/alter_view_rename.q.out
* /hive/trunk/ql/src/test/results/clientpositive/archive_corrupt.q.out
* /hive/trunk/ql/src/test/results/clientpositive/authorization_7.q.out
* /hive/trunk/ql/src/test/results/clientpositive/autogen_colalias.q.out
* /hive/trunk/ql/src/test/results/clientpositive/avro_change_schema.q.out
* /hive/trunk/ql/src/test/results/clientpositive/avro_evolved_schemas.q.out
* /hive/trunk/ql/src/test/results/clientpositive/avro_joins.q.out
* /hive/trunk/ql/src/test/results/clientpositive/avro_sanity_test.q.out
* /hive/trunk/ql/src/test/results/clientpositive/avro_schema_error_message.q.out
* /hive/trunk/ql/src/test/results/clientpositive/avro_schema_literal.q.out
* /hive/trunk/ql/src/test/results/clientpositive/ba_table1.q.out
* /hive/trunk/ql/src/test/results/clientpositive/ba_table2.q.out
* /hive/trunk/ql/src/test/results/clientpositive/ba_table_union.q.out
* /hive/trunk/ql/src/test/results/clientpositive/binary_table_bincolserde.q.out
* /hive/trunk/ql/src/test/results/clientpositive/binary_table_colserde.q.out
* /hive/trunk/ql/src/test/results/clientpositive/bucket_groupby.q.out
* 
/hive/trunk/ql/src/test/results/clientpositive/columnarserde_create_shortcut.q.out
* /hive/trunk/ql/src/test/results/clientpositive/combine3.q.out
* /hive/trunk/ql/src/test/results/clientpositive/convert_enum_to_string.q.out
* /hive/trunk/ql/src/test/results/clientpositive/create_1.q.out
* /hive/trunk/ql/src/test/results/clientpositive/create_default_prop.q.out
* /hive/trunk/ql/src/test/results/clientpositive/create_escape.q.out
* 
/hive/trunk/ql/src/test/results/clientpositive/create_insert_outputformat.q.out
* /hive/trunk/ql/src/test/results/clientpositive/create_like_view.q.out
* /hive/trunk/ql/src/test/results/clientpositive/create_nested_type.q.out
* /hive/trunk/ql/src/test/results/clientpositive/create_view.q.out
* /hive/trunk/ql/src/test/results/clientpositive/create_view_partitioned.q.out
* /hive/trunk/ql/src/test/results/clientpositive/database.q.out
* /hive/trunk/ql/src/test/results/clientpositive/ddltime.q.out
* /hive/trunk/ql/src/test/results/clientpositive/describe_comment_indent.q.out
* /hive/trunk/ql/src/test/results/clientpositive/describe_syntax.q.out
* /hive/trunk/ql/src/test/results/clie

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

2012-12-07 Thread Apache Jenkins Server

See 

Changes:

[hashutosh] HIVE-3384 : HIVE JDBC module won't compile under JDK1.7 as new 
methods added in JDBC specification (Shengsheng Huang, Chris Drome, Mikhail 
Bautin via Ashutosh Chauhan)

--
[...truncated 36623 lines...]
[junit] POSTHOOK: Output: 
file:/tmp/jenkins/hive_2012-12-07_18-35-24_373_8871850726258245429/-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=/x1/jenkins/jenkins-slave/workspace/Hive-0.9.1-SNAPSHOT-h0.21/hive/build/service/tmp/hive_job_log_jenkins_201212071835_1920837102.txt
[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] Copying file: 
file:/x1/jenkins/jenkins-slave/workspace/Hive-0.9.1-SNAPSHOT-h0.21/hive/data/files/kv1.txt
[junit] POSTHOOK: query: create table testhivedrivertable (num int)
[junit] POSTHOOK: type: DROPTABLE
[junit] POSTHOOK: Output: default@testhivedrivertable
[junit] OK
[junit] PREHOOK: query: load data local inpath 
'/x1/jenkins/jenkins-slave/workspace/Hive-0.9.1-SNAPSHOT-h0.21/hive/data/files/kv1.txt'
 into table testhivedrivertable
[junit] PREHOOK: type: DROPTABLE
[junit] PREHOOK: Output: default@testhivedrivertable
[junit] Copying data from 
file:/x1/jenkins/jenkins-slave/workspace/Hive-0.9.1-SNAPSHOT-h0.21/hive/data/files/kv1.txt
[junit] Loading data to table default.testhivedrivertable
[junit] POSTHOOK: query: load data local inpath 
'/x1/jenkins/jenkins-slave/workspace/Hive-0.9.1-SNAPSHOT-h0.21/hive/data/files/kv1.txt'
 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/jenkins/hive_2012-12-07_18-35-28_294_8660802367417257327/-mr-1
[junit] POSTHOOK: query: select * from testhivedrivertable limit 10
[junit] POSTHOOK: type: DROPTABLE
[junit] POSTHOOK: Input: default@testhivedrivertable
[junit] POSTHOOK: Output: 
file:/tmp/jenkins/hive_2012-12-07_18-35-28_294_8660802367417257327/-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=/x1/jenkins/jenkins-slave/workspace/Hive-0.9.1-SNAPSHOT-h0.21/hive/build/service/tmp/hive_job_log_jenkins_201212071835_1632695301.txt
[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=/x1/jenkins/jenkins-slave/workspace/Hive-0.9.1-SNAPSHOT-h0.21/hive/build/service/tmp/hive_job_log_jenkins_201212071835_299542925.txt
[junit] Hive history 
file=/x1/jenkins/jenkins-slave/workspace/Hive-0.9.1-SNAPSHOT-h0.21/hive/build/service/tmp/hive_job_log_jenkins_201212071835_1360282042.txt
[junit] Copying file: 
file:/x1/jenkins/jenkins-slave/workspace/Hive-0.9.1-SNAPSHOT-h0.21/hive/data/files/kv1.txt
[junit] PREHOOK: query: drop t

[jira] [Commented] (HIVE-3384) HIVE JDBC module won't compile under JDK1.7 as new methods added in JDBC specification

2012-12-07 Thread Hudson (JIRA)


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

Hudson commented on HIVE-3384:
--

Integrated in Hive-0.9.1-SNAPSHOT-h0.21 #222 (See 
[https://builds.apache.org/job/Hive-0.9.1-SNAPSHOT-h0.21/222/])
HIVE-3384 : HIVE JDBC module won't compile under JDK1.7 as new methods 
added in JDBC specification (Shengsheng Huang, Chris Drome, Mikhail Bautin via 
Ashutosh Chauhan) (Revision 1418384)

 Result = FAILURE
hashutosh : 
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1418384
Files : 
* /hive/branches/branch-0.9/build-common.xml
* /hive/branches/branch-0.9/build.properties
* 
/hive/branches/branch-0.9/jdbc/src/java/org/apache/hadoop/hive/jdbc/HiveBaseResultSet.java
* 
/hive/branches/branch-0.9/jdbc/src/java/org/apache/hadoop/hive/jdbc/HiveCallableStatement.java
* 
/hive/branches/branch-0.9/jdbc/src/java/org/apache/hadoop/hive/jdbc/HiveConnection.java
* 
/hive/branches/branch-0.9/jdbc/src/java/org/apache/hadoop/hive/jdbc/HiveDataSource.java
* 
/hive/branches/branch-0.9/jdbc/src/java/org/apache/hadoop/hive/jdbc/HiveDatabaseMetaData.java
* 
/hive/branches/branch-0.9/jdbc/src/java/org/apache/hadoop/hive/jdbc/HiveDriver.java
* 
/hive/branches/branch-0.9/jdbc/src/java/org/apache/hadoop/hive/jdbc/HivePreparedStatement.java
* 
/hive/branches/branch-0.9/jdbc/src/java/org/apache/hadoop/hive/jdbc/HiveQueryResultSet.java
* 
/hive/branches/branch-0.9/jdbc/src/java/org/apache/hadoop/hive/jdbc/HiveStatement.java
* /hive/branches/branch-0.9/metastore/build.xml
* /hive/branches/branch-0.9/pdk/scripts/build-plugin.xml


> HIVE JDBC module won't compile under JDK1.7 as new methods added in JDBC 
> specification
> --
>
> Key: HIVE-3384
> URL: https://issues.apache.org/jira/browse/HIVE-3384
> Project: Hive
>  Issue Type: Bug
>  Components: JDBC
>Reporter: Weidong Bian
>Assignee: Mikhail Bautin
>Priority: Minor
> Fix For: 0.11
>
> Attachments: D6873-0.9.1.patch, D6873.1.patch, D6873.2.patch, 
> D6873.3.patch, D6873.4.patch, D6873.5.patch, D6873.6.patch, D6873.7.patch, 
> HIVE-3384-2012-12-02.patch, HIVE-3384-2012-12-04.patch, HIVE-3384.2.patch, 
> HIVE-3384-branch-0.9.patch, HIVE-3384.patch, HIVE-JDK7-JDBC.patch
>
>
> jdbc module couldn't be compiled with jdk7 as it adds some abstract method in 
> the JDBC specification 
> some error info:
>  error: HiveCallableStatement is not abstract and does not override abstract
> method getObject(String,Class) in CallableStatement
> .
> .
> .

--
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-3705) Adding authorization capability to the metastore

2012-12-07 Thread Sushanth Sowmyan (JIRA)


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

Sushanth Sowmyan updated HIVE-3705:
---

Attachment: HIVE-3705.giant.svn.patch

Attaching monolithic patch generated from svn trunk to make applying easier.

> Adding authorization capability to the metastore
> 
>
> Key: HIVE-3705
> URL: https://issues.apache.org/jira/browse/HIVE-3705
> Project: Hive
>  Issue Type: New Feature
>  Components: Authorization, Metastore
>Reporter: Sushanth Sowmyan
>Assignee: Sushanth Sowmyan
> Attachments: HIVE-3705.D6681.1.patch, HIVE-3705.D6681.2.patch, 
> HIVE-3705.D6681.3.patch, HIVE-3705.D6681.4.patch, HIVE-3705.D6681.5.patch, 
> HIVE-3705.giant.svn.patch, hive-backend-auth.2.git.patch, 
> hive-backend-auth.git.patch, hive-backend-auth.post-review.git.patch, 
> hive-backend-auth.post-review-part2.git.patch, 
> hive-backend-auth.post-review-part3.git.patch, hivesec_investigation.pdf
>
>
> In an environment where multiple clients access a single metastore, and we 
> want to evolve hive security to a point where it's no longer simply 
> preventing users from shooting their own foot, we need to be able to 
> authorize metastore calls as well, instead of simply performing every 
> metastore api call that's made.

--
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-3384) HIVE JDBC module won't compile under JDK1.7 as new methods added in JDBC specification

2012-12-07 Thread Chris Drome (JIRA)


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

Chris Drome commented on HIVE-3384:
---

[~mikhail]: When I checked the repository yesterday it hadn't been commited 
yet. Thanks Ashutosh.

> HIVE JDBC module won't compile under JDK1.7 as new methods added in JDBC 
> specification
> --
>
> Key: HIVE-3384
> URL: https://issues.apache.org/jira/browse/HIVE-3384
> Project: Hive
>  Issue Type: Bug
>  Components: JDBC
>Reporter: Weidong Bian
>Assignee: Mikhail Bautin
>Priority: Minor
> Fix For: 0.11
>
> Attachments: D6873-0.9.1.patch, D6873.1.patch, D6873.2.patch, 
> D6873.3.patch, D6873.4.patch, D6873.5.patch, D6873.6.patch, D6873.7.patch, 
> HIVE-3384-2012-12-02.patch, HIVE-3384-2012-12-04.patch, HIVE-3384.2.patch, 
> HIVE-3384-branch-0.9.patch, HIVE-3384.patch, HIVE-JDK7-JDBC.patch
>
>
> jdbc module couldn't be compiled with jdk7 as it adds some abstract method in 
> the JDBC specification 
> some error info:
>  error: HiveCallableStatement is not abstract and does not override abstract
> method getObject(String,Class) in CallableStatement
> .
> .
> .

--
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-3384) HIVE JDBC module won't compile under JDK1.7 as new methods added in JDBC specification

2012-12-07 Thread Mikhail Bautin (JIRA)


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

Mikhail Bautin commented on HIVE-3384:
--

[~cdrome]: I think this patch has already been committed to 0.9 (thanks 
[~ashutoshc]!), and we need to deal with remaining test failures separately.

> HIVE JDBC module won't compile under JDK1.7 as new methods added in JDBC 
> specification
> --
>
> Key: HIVE-3384
> URL: https://issues.apache.org/jira/browse/HIVE-3384
> Project: Hive
>  Issue Type: Bug
>  Components: JDBC
>Reporter: Weidong Bian
>Assignee: Mikhail Bautin
>Priority: Minor
> Fix For: 0.11
>
> Attachments: D6873-0.9.1.patch, D6873.1.patch, D6873.2.patch, 
> D6873.3.patch, D6873.4.patch, D6873.5.patch, D6873.6.patch, D6873.7.patch, 
> HIVE-3384-2012-12-02.patch, HIVE-3384-2012-12-04.patch, HIVE-3384.2.patch, 
> HIVE-3384-branch-0.9.patch, HIVE-3384.patch, HIVE-JDK7-JDBC.patch
>
>
> jdbc module couldn't be compiled with jdk7 as it adds some abstract method in 
> the JDBC specification 
> some error info:
>  error: HiveCallableStatement is not abstract and does not override abstract
> method getObject(String,Class) in CallableStatement
> .
> .
> .

--
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-3781) not all meta events call metastore event listener

2012-12-07 Thread Sudhanshu Arora (JIRA)

Sudhanshu Arora created HIVE-3781:
-

 Summary: not all meta events call metastore event listener
 Key: HIVE-3781
 URL: https://issues.apache.org/jira/browse/HIVE-3781
 Project: Hive
  Issue Type: Bug
  Components: Metastore
Affects Versions: 0.9.0
Reporter: Sudhanshu Arora


An event listener must be called for any DDL activity. For example, 
create_index, drop_index today does not call metaevent listener. 

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

Jenkins build is back to normal : Hive-0.9.1-SNAPSHOT-h0.21 #221

2012-12-07 Thread Apache Jenkins Server

See

[jira] [Commented] (HIVE-3594) When Group by Partition Column Type is Timestamp or STRING Which Format contains "HH:MM:SS", It will occur URISyntaxException

2012-12-07 Thread Kevin Wilfong (JIRA)


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

Kevin Wilfong commented on HIVE-3594:
-

I realize I'm late, but when you replaced the URLEncoder with a replaceAll, 
won't you end up creating the same path for two partitions part=a: and part=a# 
and does this matter (I'm not too familiar with the metadata only query code).

> When Group by Partition Column Type is Timestamp or STRING Which Format 
> contains "HH:MM:SS", It will occur URISyntaxException
> -
>
> Key: HIVE-3594
> URL: https://issues.apache.org/jira/browse/HIVE-3594
> Project: Hive
>  Issue Type: Bug
>  Components: Query Processor
>Reporter: Daisy.Yuan
>Assignee: Navis
> Attachments: HIVE-3594.D6081.1.patch, HIVE-3594.D6081.2.patch
>
>
> create table test (no int, name string) partitioned by (pts string) row 
> format delimited fields terminated by ' '; 
> load data local inpath '/opt/files/groupbyts1.txt' into table test 
> partition(pts='12:11:30');
> load data local inpath '/opt/files/groupbyts2.txt' into table test 
> partition(pts='21:25:12');
> load data local inpath '/opt/files/groupbyts3.txt' into table test 
> partition(pts='12:11:30');
> load data local inpath '/opt/files/groupbyts4.txt' into table test 
> partition(pts='21:25:12');
> when I execute “select * from test group by pts;”, it will occur as follows 
> exception.
>  at org.apache.hadoop.fs.Path.initialize(Path.java:157)
> at org.apache.hadoop.fs.Path.(Path.java:135)
> at 
> org.apache.hadoop.hive.ql.exec.Utilities.getInputSummary(Utilities.java:1667)
> at 
> org.apache.hadoop.hive.ql.exec.MapRedTask.estimateNumberOfReducers(MapRedTask.java:432)
> at 
> org.apache.hadoop.hive.ql.exec.MapRedTask.setNumberOfReducers(MapRedTask.java:400)
> at 
> org.apache.hadoop.hive.ql.exec.MapRedTask.execute(MapRedTask.java:93)
> 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.service.HiveServer$HiveServerHandler.execute(HiveServer.java:198)
> at 
> org.apache.hadoop.hive.service.ThriftHive$Processor$execute.getResult(ThriftHive.java:630)
> at 
> org.apache.hadoop.hive.service.ThriftHive$Processor$execute.getResult(ThriftHive.java:618)
> 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.net.URISyntaxException: Relative path in absolute URI: 
> fake-path-metadata-only-query-default.test{pts=12:11:30%7D
> at java.net.URI.checkPath(URI.java:1788)
> at java.net.URI.(URI.java:734)
> at org.apache.hadoop.fs.Path.initialize(Path.java:154)
> ... 19 more
> FAILED: Execution Error, return code 1 from 
> org.apache.hadoop.hive.ql.exec.MapRedTask
> When PhysicalOptimizer optimizes GroupByOperator, according to default 
> parameters "hive.optimize.metadataonly = true", MetadataOnlyOptimizer will be 
> enabled. The MetadataOnlyOptimizer will change the partition alias desc. The 
> partition alies "hdfs://ip:9000/user/hive/warehouse/test/pts=12%3A11%3A30" is 
> changed into " 
> fake-path-metadata-only-query-default.test{pts=12:11:30}". When construct uri 
> through new partition alies, it must occur java.net.URISyntaxException. 
>  

--
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-2723) should throw "Ambiguous column reference key" Exception in particular join condition

2012-12-07 Thread Kevin Wilfong (JIRA)


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

Kevin Wilfong commented on HIVE-2723:
-

Hi, I realize I'm a little late but why should the following query fail (from 
the clientnegative test cases)?

explain select * from (select * from (select * from src) a join (select * from 
src1) b on (a.key = b.key)) t;

> should throw  "Ambiguous column reference key"  Exception in particular join 
> condition
> --
>
> Key: HIVE-2723
> URL: https://issues.apache.org/jira/browse/HIVE-2723
> Project: Hive
>  Issue Type: Bug
>  Components: Query Processor
> Environment: Linux zongren-VirtualBox 3.0.0-14-generic #23-Ubuntu SMP 
> Mon Nov 21 20:34:47 UTC 2011 i686 i686 i386 GNU/Linux
> java version "1.6.0_25"
> hadoop-0.20.2-cdh3u0
> hive-0.7.0-cdh3u0
>Reporter: caofangkun
>Assignee: Navis
>Priority: Minor
>  Labels: exception-handling, query, queryparser
> Attachments: ASF.LICENSE.NOT.GRANTED--HIVE-2723.D1275.1.patch, 
> ASF.LICENSE.NOT.GRANTED--HIVE-2723.D1275.2.patch, hive.2723.1.patch, 
> HIVE-2723.D1275.3.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-3780) RetryingMetaStoreClient Should Log the Caught Exception

2012-12-07 Thread Bhushan Mandhani (JIRA)


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

Bhushan Mandhani updated HIVE-3780:
---

Status: Patch Available  (was: Open)

> RetryingMetaStoreClient Should Log the Caught Exception
> ---
>
> Key: HIVE-3780
> URL: https://issues.apache.org/jira/browse/HIVE-3780
> Project: Hive
>  Issue Type: Bug
>Reporter: Bhushan Mandhani
>Assignee: Bhushan Mandhani
>Priority: Trivial
> Attachments: HIVE-3780.1.patch.txt
>
>
> Currently it logs the cause of the caught exception. It should log the caught 
> exception itself.

--
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-3780) RetryingMetaStoreClient Should Log the Caught Exception

2012-12-07 Thread Bhushan Mandhani (JIRA)


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

Bhushan Mandhani updated HIVE-3780:
---

Attachment: HIVE-3780.1.patch.txt

> RetryingMetaStoreClient Should Log the Caught Exception
> ---
>
> Key: HIVE-3780
> URL: https://issues.apache.org/jira/browse/HIVE-3780
> Project: Hive
>  Issue Type: Bug
>Reporter: Bhushan Mandhani
>Assignee: Bhushan Mandhani
>Priority: Trivial
> Attachments: HIVE-3780.1.patch.txt
>
>
> Currently it logs the cause of the caught exception. It should log the caught 
> exception itself.

--
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-3780) RetryingMetaStoreClient Should Log the Caught Exception

2012-12-07 Thread Bhushan Mandhani (JIRA)


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

Bhushan Mandhani commented on HIVE-3780:


Diff out at https://reviews.facebook.net/D7239

> RetryingMetaStoreClient Should Log the Caught Exception
> ---
>
> Key: HIVE-3780
> URL: https://issues.apache.org/jira/browse/HIVE-3780
> Project: Hive
>  Issue Type: Bug
>Reporter: Bhushan Mandhani
>Assignee: Bhushan Mandhani
>Priority: Trivial
>
> Currently it logs the cause of the caught exception. It should log the caught 
> exception itself.

--
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] [Assigned] (HIVE-3780) RetryingMetaStoreClient Should Log the Caught Exception

2012-12-07 Thread Bhushan Mandhani (JIRA)


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

Bhushan Mandhani reassigned HIVE-3780:
--

Assignee: Bhushan Mandhani

> RetryingMetaStoreClient Should Log the Caught Exception
> ---
>
> Key: HIVE-3780
> URL: https://issues.apache.org/jira/browse/HIVE-3780
> Project: Hive
>  Issue Type: Bug
>Reporter: Bhushan Mandhani
>Assignee: Bhushan Mandhani
>Priority: Trivial
>
> Currently it logs the cause of the caught exception. It should log the caught 
> exception itself.

--
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 # 1841 - Still Failing

2012-12-07 Thread Apache Jenkins Server

Changes for Build #1831
[namit] HIVE-3747 Provide hive operation name for hookContext
(Shreepadma Venugopalan via namit)


Changes for Build #1832

Changes for Build #1833
[namit] HIVE-3750 JDBCStatsPublisher fails when ID length exceeds length of ID 
column
(Kevin Wilfong via namit)


Changes for Build #1835
[namit] HIVE-3073 Hive List Bucketing - DML support
(Gang Tim Liu via namit)

[namit] HIVE-3771 HIVE-3750 broke TestParse
(Kevin Wilfong via namit)

[hashutosh] HIVE-3384 : HIVE JDBC module won't compile under JDK1.7 as new 
methods added in JDBC specification (Shengsheng Huang, Chris Drome, Mikhail 
Bautin via Ashutosh Chauhan)

[namit] HIVE-3702 Renaming table changes table location scheme/authority
(Kevin Wilfong via namit)


Changes for Build #1836
[namit] HIVE-2723 should throw "Ambiguous column reference key" Exception in 
particular
join condition (Navis via namit)

[namit] HIVE-3594 When Group by Partition Column Type is Timestamp or STRING 
Which Format contains "HH:MM:SS",
It will occur URISyntaxException (Navis via namit)


Changes for Build #1837
[namit] HIVE-3762 Minor fix for 'tableName' in Hive.g
(Navis via namit)


Changes for Build #1838

Changes for Build #1839
[namit] HIVE-2477 Use name of original expression for name of CAST output
(Navis via namit)


Changes for Build #1840
[hashutosh] HIVE-3400 : Add Retries to Hive MetaStore Connections (Bhushan 
Mandhani via Ashutosh Chauhan)


Changes for Build #1841
[namit] HIVE-3767 BucketizedHiveInputFormat should be automatically used with 
Bucketized Map Joins also (Gang Tim Liu via namit)




1 tests failed.
FAILED:  org.apache.hadoop.hive.cli.TestCliDriver.testCliDriver_stats19

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.TestCliDriver.testCliDriver_stats19(TestCliDriver.java:41260)
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:518)
at 
org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.launch(JUnitTestRunner.java:1052)
at 
org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.main(JUnitTestRunner.java:906)




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

Status: Still Failing

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

[jira] [Commented] (HIVE-3767) BucketizedHiveInputFormat should be automatically used with Bucketized Map Joins also

2012-12-07 Thread Hudson (JIRA)


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

Hudson commented on HIVE-3767:
--

Integrated in Hive-trunk-h0.21 #1841 (See 
[https://builds.apache.org/job/Hive-trunk-h0.21/1841/])
HIVE-3767 BucketizedHiveInputFormat should be automatically used with 
Bucketized Map Joins also (Gang Tim Liu via namit) (Revision 1418286)

 Result = FAILURE
namit : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1418286
Files : 
* 
/hive/trunk/ql/src/java/org/apache/hadoop/hive/ql/optimizer/BucketMapJoinOptimizer.java
* 
/hive/trunk/ql/src/java/org/apache/hadoop/hive/ql/optimizer/GenMapRedUtils.java
* /hive/trunk/ql/src/java/org/apache/hadoop/hive/ql/plan/MapJoinDesc.java
* /hive/trunk/ql/src/test/queries/clientpositive/bucket_map_join_1.q
* /hive/trunk/ql/src/test/queries/clientpositive/bucket_map_join_2.q
* /hive/trunk/ql/src/test/queries/clientpositive/bucketmapjoin13.q
* /hive/trunk/ql/src/test/queries/clientpositive/bucketmapjoin6.q


> BucketizedHiveInputFormat should be automatically used with Bucketized Map 
> Joins also
> -
>
> Key: HIVE-3767
> URL: https://issues.apache.org/jira/browse/HIVE-3767
> Project: Hive
>  Issue Type: Bug
>  Components: Query Processor
>Reporter: Namit Jain
>Assignee: Gang Tim Liu
> Attachments: HIVE-3767.patch.2
>
>
> It seems like even after https://issues.apache.org/jira/browse/HIVE-3219 we 
> still need to set hive.input.format = 
> org.apache.hadoop.hive.ql.io.BucketizedHiveInputFormat for bucket map joins 
> (though not SMB joins)

--
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-3780) RetryingMetaStoreClient Should Log the Caught Exception

2012-12-07 Thread Bhushan Mandhani (JIRA)

Bhushan Mandhani created HIVE-3780:
--

 Summary: RetryingMetaStoreClient Should Log the Caught Exception
 Key: HIVE-3780
 URL: https://issues.apache.org/jira/browse/HIVE-3780
 Project: Hive
  Issue Type: Bug
Reporter: Bhushan Mandhani
Priority: Trivial


Currently it logs the cause of the caught exception. It should log the caught 
exception itself.

--
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-3384) HIVE JDBC module won't compile under JDK1.7 as new methods added in JDBC specification

2012-12-07 Thread Chris Drome (JIRA)


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

Chris Drome commented on HIVE-3384:
---

[~ashutoshc]: I think the failure is occuring as a result of HIVE-3435 not 
being applied to branch 0.9 as opposed to new failures being caused by this 
test.

How do we proceed in that case? Do we need to backport that patch and get it to 
succeed before moving forward with this one?

> HIVE JDBC module won't compile under JDK1.7 as new methods added in JDBC 
> specification
> --
>
> Key: HIVE-3384
> URL: https://issues.apache.org/jira/browse/HIVE-3384
> Project: Hive
>  Issue Type: Bug
>  Components: JDBC
>Reporter: Weidong Bian
>Assignee: Mikhail Bautin
>Priority: Minor
> Fix For: 0.11
>
> Attachments: D6873-0.9.1.patch, D6873.1.patch, D6873.2.patch, 
> D6873.3.patch, D6873.4.patch, D6873.5.patch, D6873.6.patch, D6873.7.patch, 
> HIVE-3384-2012-12-02.patch, HIVE-3384-2012-12-04.patch, HIVE-3384.2.patch, 
> HIVE-3384-branch-0.9.patch, HIVE-3384.patch, HIVE-JDK7-JDBC.patch
>
>
> jdbc module couldn't be compiled with jdk7 as it adds some abstract method in 
> the JDBC specification 
> some error info:
>  error: HiveCallableStatement is not abstract and does not override abstract
> method getObject(String,Class) in CallableStatement
> .
> .
> .

--
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] [Assigned] (HIVE-3763) Aggregation followed by a sort-merge join requires a new MR job

2012-12-07 Thread Namit Jain (JIRA)


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

Namit Jain reassigned HIVE-3763:


Assignee: Namit Jain

> Aggregation followed by a sort-merge join requires a new MR job
> ---
>
> Key: HIVE-3763
> URL: https://issues.apache.org/jira/browse/HIVE-3763
> Project: Hive
>  Issue Type: Bug
>Reporter: Namit Jain
>Assignee: Namit Jain
>
> After Hive-3633, if tbl1 and tbl2 are tables bucketiezed and sorted by key 
> into 2 buckets, the following query:
>   
>   
> select count(*) from (
>   select /*+mapjoin(a)*/ a.key as key, a.value as val1, b.value as val2 from 
> tbl1 a join tbl2 b on a.key = b.key
> ) subq1;  
> requires 2 MR job - the first one is a sort-merge join, and the second MR job
> performs the count(*) on the output of the sort-merge join. 
> Ideally, this should be performed in a single MR 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

[jira] [Assigned] (HIVE-3160) All temporary functions should be dropped at the end of each .q file

2012-12-07 Thread Namit Jain (JIRA)


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

Namit Jain reassigned HIVE-3160:


Assignee: Srinivas Vemuri

> All temporary functions should be dropped at the end of each .q file
> 
>
> Key: HIVE-3160
> URL: https://issues.apache.org/jira/browse/HIVE-3160
> Project: Hive
>  Issue Type: Bug
>  Components: Testing Infrastructure
>Affects Versions: 0.9.0
>Reporter: Namit Jain
>Assignee: Srinivas Vemuri
>
> Currently, only the tables and databases are dropped.
> A test like show_functions.q can get intermittent errors.

--
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] [Assigned] (HIVE-3162) Implement SHOW TEMPORARY FUNCTIONS

2012-12-07 Thread Namit Jain (JIRA)


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

Namit Jain reassigned HIVE-3162:


Assignee: Srinivas Vemuri

> Implement SHOW TEMPORARY FUNCTIONS
> --
>
> Key: HIVE-3162
> URL: https://issues.apache.org/jira/browse/HIVE-3162
> Project: Hive
>  Issue Type: Bug
>  Components: SQL
>Reporter: Carl Steinbach
>Assignee: Srinivas Vemuri
>


--
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] [Assigned] (HIVE-3445) Skewed join optimization for different datatypes

2012-12-07 Thread Namit Jain (JIRA)


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

Namit Jain reassigned HIVE-3445:


Assignee: Srinivas Vemuri  (was: Namit Jain)

> Skewed join optimization for different datatypes
> 
>
> Key: HIVE-3445
> URL: https://issues.apache.org/jira/browse/HIVE-3445
> Project: Hive
>  Issue Type: Bug
>  Components: Query Processor
>Reporter: Namit Jain
>Assignee: Srinivas Vemuri
>


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

2012-12-07 Thread Apache Jenkins Server

See 


Changes:

[hashutosh] HIVE-3384 : HIVE JDBC module won't compile under JDK1.7 as new 
methods added in JDBC specification (Shengsheng Huang, Chris Drome, Mikhail 
Bautin via Ashutosh Chauhan)

--
[...truncated 9917 lines...]
compile-test:
 [echo] Project: serde
[javac] Compiling 26 source files to 

[javac] Note: Some input files use or override a deprecated API.
[javac] Note: Recompile with -Xlint:deprecation for details.
[javac] Note: Some input files use unchecked or unsafe operations.
[javac] Note: Recompile with -Xlint:unchecked for details.

create-dirs:
 [echo] Project: service
 [copy] Warning: 

 does not exist.

init:
 [echo] Project: service

ivy-init-settings:
 [echo] Project: service

ivy-resolve:
 [echo] Project: service
[ivy:resolve] :: loading settings :: file = 

[ivy:report] Processing 

 to 


ivy-retrieve:
 [echo] Project: service

compile:
 [echo] Project: service

ivy-resolve-test:
 [echo] Project: service

ivy-retrieve-test:
 [echo] Project: service

compile-test:
 [echo] Project: service
[javac] Compiling 2 source files to 


test:
 [echo] Project: hive

test-shims:
 [echo] Project: hive

test-conditions:
 [echo] Project: shims

gen-test:
 [echo] Project: shims

create-dirs:
 [echo] Project: shims
 [copy] Warning: 

 does not exist.

init:
 [echo] Project: shims

ivy-init-settings:
 [echo] Project: shims

ivy-resolve:
 [echo] Project: shims
[ivy:resolve] :: loading settings :: file = 

[ivy:report] Processing 

 to 


ivy-retrieve:
 [echo] Project: shims

compile:
 [echo] Project: shims
 [echo] Building shims 0.20

build_shims:
 [echo] Project: shims
 [echo] Compiling 

 against hadoop 0.20.2 
(

ivy-init-settings:
 [echo] Project: shims

ivy-resolve-hadoop-shim:
 [echo] Project: shims
[ivy:resolve] :: loading settings :: file = 


ivy-retrieve-hadoop-shim:
 [echo] Project: shims
 [echo] Building shims 0.20S

build_shims:
 [echo] Project: shims
 [echo] Compiling 

 against hadoop 1.0.0 
(

ivy-init-settings:
 [echo] Project: shims

ivy-resolve-hadoop-shim:
 [echo] Project: shims
[ivy:resolve] :: loading settings :: file = 


ivy-retrieve-hadoop-shim:
 [echo] Project: shims
 [echo] Building shims 0.23

build_shims:
 [echo] Project: shims
 [echo] Compiling

[jira] [Assigned] (HIVE-3296) comments before a set statement in a test do not work

2012-12-07 Thread Namit Jain (JIRA)


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

Namit Jain reassigned HIVE-3296:


Assignee: Srinivas Vemuri  (was: Namit Jain)

> comments before a set statement in a test do not work
> -
>
> Key: HIVE-3296
> URL: https://issues.apache.org/jira/browse/HIVE-3296
> Project: Hive
>  Issue Type: Bug
>  Components: Testing Infrastructure
>Reporter: Namit Jain
>Assignee: Srinivas Vemuri
>
> The following test fails:::
> -- test comment
> set hive.test="foo";
> create table tst(key string);
> The output is::
> FAILED: ParseException line 2:0 cannot recognize input near 'set' 'hive' '.'
> However, if the comment position is changed it works fine.
> The following test:
> -- test comment
> create table tst(key string);
> set hive.test="foo";
> works fine

--
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-3384) HIVE JDBC module won't compile under JDK1.7 as new methods added in JDBC specification

2012-12-07 Thread Hudson (JIRA)


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

Hudson commented on HIVE-3384:
--

Integrated in Hive-0.9.1-SNAPSHOT-h0.21-keepgoing=false #222 (See 
[https://builds.apache.org/job/Hive-0.9.1-SNAPSHOT-h0.21-keepgoing=false/222/])
HIVE-3384 : HIVE JDBC module won't compile under JDK1.7 as new methods 
added in JDBC specification (Shengsheng Huang, Chris Drome, Mikhail Bautin via 
Ashutosh Chauhan) (Revision 1418384)

 Result = FAILURE
hashutosh : 
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1418384
Files : 
* /hive/branches/branch-0.9/build-common.xml
* /hive/branches/branch-0.9/build.properties
* 
/hive/branches/branch-0.9/jdbc/src/java/org/apache/hadoop/hive/jdbc/HiveBaseResultSet.java
* 
/hive/branches/branch-0.9/jdbc/src/java/org/apache/hadoop/hive/jdbc/HiveCallableStatement.java
* 
/hive/branches/branch-0.9/jdbc/src/java/org/apache/hadoop/hive/jdbc/HiveConnection.java
* 
/hive/branches/branch-0.9/jdbc/src/java/org/apache/hadoop/hive/jdbc/HiveDataSource.java
* 
/hive/branches/branch-0.9/jdbc/src/java/org/apache/hadoop/hive/jdbc/HiveDatabaseMetaData.java
* 
/hive/branches/branch-0.9/jdbc/src/java/org/apache/hadoop/hive/jdbc/HiveDriver.java
* 
/hive/branches/branch-0.9/jdbc/src/java/org/apache/hadoop/hive/jdbc/HivePreparedStatement.java
* 
/hive/branches/branch-0.9/jdbc/src/java/org/apache/hadoop/hive/jdbc/HiveQueryResultSet.java
* 
/hive/branches/branch-0.9/jdbc/src/java/org/apache/hadoop/hive/jdbc/HiveStatement.java
* /hive/branches/branch-0.9/metastore/build.xml
* /hive/branches/branch-0.9/pdk/scripts/build-plugin.xml


> HIVE JDBC module won't compile under JDK1.7 as new methods added in JDBC 
> specification
> --
>
> Key: HIVE-3384
> URL: https://issues.apache.org/jira/browse/HIVE-3384
> Project: Hive
>  Issue Type: Bug
>  Components: JDBC
>Reporter: Weidong Bian
>Assignee: Mikhail Bautin
>Priority: Minor
> Fix For: 0.11
>
> Attachments: D6873-0.9.1.patch, D6873.1.patch, D6873.2.patch, 
> D6873.3.patch, D6873.4.patch, D6873.5.patch, D6873.6.patch, D6873.7.patch, 
> HIVE-3384-2012-12-02.patch, HIVE-3384-2012-12-04.patch, HIVE-3384.2.patch, 
> HIVE-3384-branch-0.9.patch, HIVE-3384.patch, HIVE-JDK7-JDBC.patch
>
>
> jdbc module couldn't be compiled with jdk7 as it adds some abstract method in 
> the JDBC specification 
> some error info:
>  error: HiveCallableStatement is not abstract and does not override abstract
> method getObject(String,Class) in CallableStatement
> .
> .
> .

--
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-3140) Comment indenting is broken for "describe" in CLI

2012-12-07 Thread Namit Jain (JIRA)


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

Namit Jain updated HIVE-3140:
-

  Resolution: Fixed
Hadoop Flags: Incompatible change,Reviewed  (was: Incompatible change)
  Status: Resolved  (was: Patch Available)

Committed. Thanks Zhenxiao

> Comment indenting is broken for "describe" in CLI
> -
>
> Key: HIVE-3140
> URL: https://issues.apache.org/jira/browse/HIVE-3140
> Project: Hive
>  Issue Type: Bug
>  Components: CLI
>Reporter: Xiaoxiao Hou
>Assignee: Zhenxiao Luo
>  Labels: patch
> Fix For: 0.10.0
>
> Attachments: HIVE-3140.1.patch.txt, HIVE-3140.2.patch.txt, 
> hive.3140.3.patch, HIVE-3140.3.patch.txt
>
>   Original Estimate: 72h
>  Remaining Estimate: 72h
>
> Just go into the CLI and type "describe [TABLE_NAME]". If a comment has 
> multiple lines, it is completely unreadable due to poor comment indenting. 
> For example:
> birthdayParam string 1 = comment1
> 2 = comment2
> 3 = comment3
> But it supposed to display as:
> birthdayParam string 1 = comment1
>  2 = comment2
>  3 = comment3
> Comments should be indented the same amount on each line, i.e., if the 
> comment starts at row k for the first line of the comment, it should be 
> indented by k on line 2.

--
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-3140) Comment indenting is broken for "describe" in CLI

2012-12-07 Thread Namit Jain (JIRA)


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

Namit Jain commented on HIVE-3140:
--

Tests succeeded with the new patch

> Comment indenting is broken for "describe" in CLI
> -
>
> Key: HIVE-3140
> URL: https://issues.apache.org/jira/browse/HIVE-3140
> Project: Hive
>  Issue Type: Bug
>  Components: CLI
>Reporter: Xiaoxiao Hou
>Assignee: Zhenxiao Luo
>  Labels: patch
> Fix For: 0.10.0
>
> Attachments: HIVE-3140.1.patch.txt, HIVE-3140.2.patch.txt, 
> hive.3140.3.patch, HIVE-3140.3.patch.txt
>
>   Original Estimate: 72h
>  Remaining Estimate: 72h
>
> Just go into the CLI and type "describe [TABLE_NAME]". If a comment has 
> multiple lines, it is completely unreadable due to poor comment indenting. 
> For example:
> birthdayParam string 1 = comment1
> 2 = comment2
> 3 = comment3
> But it supposed to display as:
> birthdayParam string 1 = comment1
>  2 = comment2
>  3 = comment3
> Comments should be indented the same amount on each line, i.e., if the 
> comment starts at row k for the first line of the comment, it should be 
> indented by k on line 2.

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

2012-12-07 Thread Apache Jenkins Server

See 


--
[...truncated 9916 lines...]

compile-test:
 [echo] Project: serde
[javac] Compiling 26 source files to 

[javac] Note: Some input files use or override a deprecated API.
[javac] Note: Recompile with -Xlint:deprecation for details.
[javac] Note: Some input files use unchecked or unsafe operations.
[javac] Note: Recompile with -Xlint:unchecked for details.

create-dirs:
 [echo] Project: service
 [copy] Warning: 

 does not exist.

init:
 [echo] Project: service

ivy-init-settings:
 [echo] Project: service

ivy-resolve:
 [echo] Project: service
[ivy:resolve] :: loading settings :: file = 

[ivy:report] Processing 

 to 


ivy-retrieve:
 [echo] Project: service

compile:
 [echo] Project: service

ivy-resolve-test:
 [echo] Project: service

ivy-retrieve-test:
 [echo] Project: service

compile-test:
 [echo] Project: service
[javac] Compiling 2 source files to 


test:
 [echo] Project: hive

test-shims:
 [echo] Project: hive

test-conditions:
 [echo] Project: shims

gen-test:
 [echo] Project: shims

create-dirs:
 [echo] Project: shims
 [copy] Warning: 

 does not exist.

init:
 [echo] Project: shims

ivy-init-settings:
 [echo] Project: shims

ivy-resolve:
 [echo] Project: shims
[ivy:resolve] :: loading settings :: file = 

[ivy:report] Processing 

 to 


ivy-retrieve:
 [echo] Project: shims

compile:
 [echo] Project: shims
 [echo] Building shims 0.20

build_shims:
 [echo] Project: shims
 [echo] Compiling 

 against hadoop 0.20.2 
(

ivy-init-settings:
 [echo] Project: shims

ivy-resolve-hadoop-shim:
 [echo] Project: shims
[ivy:resolve] :: loading settings :: file = 


ivy-retrieve-hadoop-shim:
 [echo] Project: shims
 [echo] Building shims 0.20S

build_shims:
 [echo] Project: shims
 [echo] Compiling 

 against hadoop 1.0.0 
(

ivy-init-settings:
 [echo] Project: shims

ivy-resolve-hadoop-shim:
 [echo] Project: shims
[ivy:resolve] :: loading settings :: file = 


ivy-retrieve-hadoop-shim:
 [echo] Project: shims
 [echo] Building shims 0.23

build_shims:
 [echo] Project: shims
 [echo] Compiling 

 against hadoop 0.23.3 
(

[jira] [Commented] (HIVE-3705) Adding authorization capability to the metastore

2012-12-07 Thread Sushanth Sowmyan (JIRA)


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

Sushanth Sowmyan commented on HIVE-3705:


In my setup, the phabricator-generated patch does not cleanly apply on trunk, 
so I have generated incremental patches for each of the review changes. So, to 
apply this patch in full, the following patches can be applied in order :

hive-backend-auth.2.git.patch -> hive-backend-auth.post-review.git.patch -> 
hive-backend-auth.post-review-part2.git.patch -> 
hive-backend-auth.post-review-part3.git.patch

> Adding authorization capability to the metastore
> 
>
> Key: HIVE-3705
> URL: https://issues.apache.org/jira/browse/HIVE-3705
> Project: Hive
>  Issue Type: New Feature
>  Components: Authorization, Metastore
>Reporter: Sushanth Sowmyan
>Assignee: Sushanth Sowmyan
> Attachments: HIVE-3705.D6681.1.patch, HIVE-3705.D6681.2.patch, 
> HIVE-3705.D6681.3.patch, HIVE-3705.D6681.4.patch, HIVE-3705.D6681.5.patch, 
> hive-backend-auth.2.git.patch, hive-backend-auth.git.patch, 
> hive-backend-auth.post-review.git.patch, 
> hive-backend-auth.post-review-part2.git.patch, 
> hive-backend-auth.post-review-part3.git.patch, hivesec_investigation.pdf
>
>
> In an environment where multiple clients access a single metastore, and we 
> want to evolve hive security to a point where it's no longer simply 
> preventing users from shooting their own foot, we need to be able to 
> authorize metastore calls as well, instead of simply performing every 
> metastore api call that's made.

--
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-3705) Adding authorization capability to the metastore

2012-12-07 Thread Sushanth Sowmyan (JIRA)


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

Sushanth Sowmyan updated HIVE-3705:
---

Attachment: hive-backend-auth.post-review-part3.git.patch
hive-backend-auth.post-review-part2.git.patch
hive-backend-auth.post-review.git.patch

Adding incremental patches in case the phabricator-generated patch does not 
cleanly apply (which it does not on my setup)

> Adding authorization capability to the metastore
> 
>
> Key: HIVE-3705
> URL: https://issues.apache.org/jira/browse/HIVE-3705
> Project: Hive
>  Issue Type: New Feature
>  Components: Authorization, Metastore
>Reporter: Sushanth Sowmyan
>Assignee: Sushanth Sowmyan
> Attachments: HIVE-3705.D6681.1.patch, HIVE-3705.D6681.2.patch, 
> HIVE-3705.D6681.3.patch, HIVE-3705.D6681.4.patch, HIVE-3705.D6681.5.patch, 
> hive-backend-auth.2.git.patch, hive-backend-auth.git.patch, 
> hive-backend-auth.post-review.git.patch, 
> hive-backend-auth.post-review-part2.git.patch, 
> hive-backend-auth.post-review-part3.git.patch, hivesec_investigation.pdf
>
>
> In an environment where multiple clients access a single metastore, and we 
> want to evolve hive security to a point where it's no longer simply 
> preventing users from shooting their own foot, we need to be able to 
> authorize metastore calls as well, instead of simply performing every 
> metastore api call that's made.

--
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-3705) Adding authorization capability to the metastore

2012-12-07 Thread Phabricator (JIRA)


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

Phabricator commented on HIVE-3705:
---

khorgath has commented on the revision "HIVE-3705 [jira] Adding authorization 
capability to the metastore".

INLINE COMMENTS
  
ql/src/test/org/apache/hadoop/hive/ql/security/TestAuthorizationPreEventListener.java:44
 Ashutosh, I have tried rebasing to head, and I do not see the changes in 
MetaStoreUtils that provides that function. This may probably be because I 
modify MetaStoreUtils in my patch as well, so I have updated the latest patch 
as if that were available.

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

To: JIRA, ashutoshc, khorgath


> Adding authorization capability to the metastore
> 
>
> Key: HIVE-3705
> URL: https://issues.apache.org/jira/browse/HIVE-3705
> Project: Hive
>  Issue Type: New Feature
>  Components: Authorization, Metastore
>Reporter: Sushanth Sowmyan
>Assignee: Sushanth Sowmyan
> Attachments: HIVE-3705.D6681.1.patch, HIVE-3705.D6681.2.patch, 
> HIVE-3705.D6681.3.patch, HIVE-3705.D6681.4.patch, HIVE-3705.D6681.5.patch, 
> hive-backend-auth.2.git.patch, hive-backend-auth.git.patch, 
> hivesec_investigation.pdf
>
>
> In an environment where multiple clients access a single metastore, and we 
> want to evolve hive security to a point where it's no longer simply 
> preventing users from shooting their own foot, we need to be able to 
> authorize metastore calls as well, instead of simply performing every 
> metastore api call that's made.

--
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-3705) Adding authorization capability to the metastore

2012-12-07 Thread Phabricator (JIRA)


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

Phabricator updated HIVE-3705:
--

Attachment: HIVE-3705.D6681.5.patch

khorgath updated the revision "HIVE-3705 [jira] Adding authorization capability 
to the metastore".
Reviewers: JIRA, ashutoshc

  Updating patch for documentation and testing requirements per code review.


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

AFFECTED FILES
  common/src/java/org/apache/hadoop/hive/conf/HiveConf.java
  conf/hive-default.xml.template
  metastore/src/java/org/apache/hadoop/hive/metastore/HiveMetaStore.java
  metastore/src/java/org/apache/hadoop/hive/metastore/MetaStoreUtils.java
  metastore/src/java/org/apache/hadoop/hive/metastore/Warehouse.java
  ql/src/java/org/apache/hadoop/hive/ql/metadata/HiveUtils.java
  ql/src/java/org/apache/hadoop/hive/ql/security/HadoopDefaultAuthenticator.java
  
ql/src/java/org/apache/hadoop/hive/ql/security/HadoopDefaultMetastoreAuthenticator.java
  
ql/src/java/org/apache/hadoop/hive/ql/security/HiveMetastoreAuthenticationProvider.java
  
ql/src/java/org/apache/hadoop/hive/ql/security/authorization/AuthorizationPreEventListener.java
  
ql/src/java/org/apache/hadoop/hive/ql/security/authorization/BitSetCheckedAuthorizationProvider.java
  
ql/src/java/org/apache/hadoop/hive/ql/security/authorization/DefaultHiveAuthorizationProvider.java
  
ql/src/java/org/apache/hadoop/hive/ql/security/authorization/DefaultHiveMetastoreAuthorizationProvider.java
  
ql/src/java/org/apache/hadoop/hive/ql/security/authorization/HiveAuthorizationProviderBase.java
  
ql/src/java/org/apache/hadoop/hive/ql/security/authorization/HiveMetastoreAuthorizationProvider.java
  
ql/src/java/org/apache/hadoop/hive/ql/security/authorization/StorageBasedAuthorizationProvider.java
  ql/src/java/org/apache/hadoop/hive/ql/session/SessionState.java
  
ql/src/test/org/apache/hadoop/hive/ql/security/DummyHiveMetastoreAuthorizationProvider.java
  
ql/src/test/org/apache/hadoop/hive/ql/security/InjectableDummyAuthenticator.java
  
ql/src/test/org/apache/hadoop/hive/ql/security/TestAuthorizationPreEventListener.java
  
ql/src/test/org/apache/hadoop/hive/ql/security/TestDefaultHiveMetastoreAuthorizationProvider.java

To: JIRA, ashutoshc, khorgath


> Adding authorization capability to the metastore
> 
>
> Key: HIVE-3705
> URL: https://issues.apache.org/jira/browse/HIVE-3705
> Project: Hive
>  Issue Type: New Feature
>  Components: Authorization, Metastore
>Reporter: Sushanth Sowmyan
>Assignee: Sushanth Sowmyan
> Attachments: HIVE-3705.D6681.1.patch, HIVE-3705.D6681.2.patch, 
> HIVE-3705.D6681.3.patch, HIVE-3705.D6681.4.patch, HIVE-3705.D6681.5.patch, 
> hive-backend-auth.2.git.patch, hive-backend-auth.git.patch, 
> hivesec_investigation.pdf
>
>
> In an environment where multiple clients access a single metastore, and we 
> want to evolve hive security to a point where it's no longer simply 
> preventing users from shooting their own foot, we need to be able to 
> authorize metastore calls as well, instead of simply performing every 
> metastore api call that's made.

--
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-3760) TestNegativeMinimrCliDriver_mapreduce_stack_trace.q fails on hadoop-1

2012-12-07 Thread Zhenxiao Luo (JIRA)


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

Zhenxiao Luo commented on HIVE-3760:


Sure Will do it.

> TestNegativeMinimrCliDriver_mapreduce_stack_trace.q fails on hadoop-1
> -
>
> Key: HIVE-3760
> URL: https://issues.apache.org/jira/browse/HIVE-3760
> Project: Hive
>  Issue Type: Bug
>Reporter: Ashutosh Chauhan
>Assignee: Gunther Hagleitner
> Attachments: HIVE-3760.2.patch, hive-3760.patch
>
>
> Actually functionality is working correctly, but incorrect include/exclude 
> macro in test directive is making its .q.out comparison against incorrect 
> results.

--
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] [Assigned] (HIVE-3761) TestNegativeMinimrCliDriver_mapreduce_stack_trace.q.out contains incorrect data.

2012-12-07 Thread Zhenxiao Luo (JIRA)


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

Zhenxiao Luo reassigned HIVE-3761:
--

Assignee: Zhenxiao Luo

> TestNegativeMinimrCliDriver_mapreduce_stack_trace.q.out contains incorrect 
> data.
> 
>
> Key: HIVE-3761
> URL: https://issues.apache.org/jira/browse/HIVE-3761
> Project: Hive
>  Issue Type: Bug
>Reporter: Ashutosh Chauhan
>Assignee: Zhenxiao Luo
>
> In particular, it doesn't contain the stack trace of failed job, which it 
> should. After HIVE-3760, this will run only against hadoop23, pointing out 
> problem is only on hadoop23 and not on hadoop20 or hadoop1.

--
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-3769) Must publish new Hive-0.10 artifacts to apache repository.

2012-12-07 Thread Travis Crawford (JIRA)


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

Travis Crawford commented on HIVE-3769:
---

Note its possible to publish snapshot jars to the apache snapshots repo from 
CI; we do this in HCatalog. If theres interest in doing the same for Hive I can 
help make it happen.

> Must publish new Hive-0.10 artifacts to apache repository.
> --
>
> Key: HIVE-3769
> URL: https://issues.apache.org/jira/browse/HIVE-3769
> Project: Hive
>  Issue Type: Bug
>  Components: Build Infrastructure, Thrift API
>Affects Versions: 0.10.0
>Reporter: Mithun Radhakrishnan
> Fix For: 0.10.0
>
>
> Hive-0.10 has successfully moved to Thrift-0.9. (HIVE-2715)
> Could we please also have the Hive-0.10 artifacts published on the Apache 
> Repository? Please note that the currently published artifacts are pretty 
> old. I suspect HIVE-2715 isn't available in the published artifact.
> https://repository.apache.org/content/groups/snapshots/org/apache/hive/hive-metastore/0.10.0-SNAPSHOT/

--
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-3760) TestNegativeMinimrCliDriver_mapreduce_stack_trace.q fails on hadoop-1

2012-12-07 Thread Ashutosh Chauhan (JIRA)


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

Ashutosh Chauhan commented on HIVE-3760:


[~zhenxiao] For the bonus, you can tackle HIVE-3761 : )

> TestNegativeMinimrCliDriver_mapreduce_stack_trace.q fails on hadoop-1
> -
>
> Key: HIVE-3760
> URL: https://issues.apache.org/jira/browse/HIVE-3760
> Project: Hive
>  Issue Type: Bug
>Reporter: Ashutosh Chauhan
>Assignee: Gunther Hagleitner
> Attachments: HIVE-3760.2.patch, hive-3760.patch
>
>
> Actually functionality is working correctly, but incorrect include/exclude 
> macro in test directive is making its .q.out comparison against incorrect 
> results.

--
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-3767) BucketizedHiveInputFormat should be automatically used with Bucketized Map Joins also

2012-12-07 Thread Gang Tim Liu (JIRA)


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

Gang Tim Liu commented on HIVE-3767:


Namit thanks a lot Tim




> BucketizedHiveInputFormat should be automatically used with Bucketized Map 
> Joins also
> -
>
> Key: HIVE-3767
> URL: https://issues.apache.org/jira/browse/HIVE-3767
> Project: Hive
>  Issue Type: Bug
>  Components: Query Processor
>Reporter: Namit Jain
>Assignee: Gang Tim Liu
> Attachments: HIVE-3767.patch.2
>
>
> It seems like even after https://issues.apache.org/jira/browse/HIVE-3219 we 
> still need to set hive.input.format = 
> org.apache.hadoop.hive.ql.io.BucketizedHiveInputFormat for bucket map joins 
> (though not SMB joins)

--
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-2439) Upgrade antlr version to 3.4

2012-12-07 Thread Thiruvel Thirumoolan (JIRA)


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

Thiruvel Thirumoolan updated HIVE-2439:
---

Attachment: HIVE-2439_branch9_3.patch

This patch addresses the issues related to views that were failing before. With 
this all previous failing tests pass. Early feedback welcome. Here is a 
description of the problem related to views.

UnparseTranslator() has a translation map where its possible to replace all the
text with the appropriate escaped version [say invites.ds will be replaced with
`invites`.`ds` and the entire query is processed like this and stored as
Extended text in table's metadata]. This holds all individual translations and
where they apply in the stream. The newer antlr has some conditions on
overlap. Two of the entries in this translation map can be disjoint or even the
same, but there cannot be partial overlap, which causes the exception.

Some of the entries during join_view.q: One can think of the below as 
UnparseTranslator.translations entries.

Start: Stop: Replacement Text
..
39:41:`invites`.`ds`
41:41:`ds`
43:45:`invites2`.`ds`
45:45:`ds`
..

Other translations don't seem to have a problem. Whenever SemanticAnalyser
finds that a translation is required, it will add it to the translation map. In
this case "41:41:`ds`" is being added by parseJoinCondPopulateAlias() for the
HiveParser.Identifier case. And "43:45:`invites2`.`ds`" is done by
genExprNodeDesc() after this during plan generation. So there is a duplicate 
entry. UnparseTranslator.addTranslation() has logic to eliminate subsets but 
seem to miss this. Have included this situation in the patch.

> Upgrade antlr version to 3.4
> 
>
> Key: HIVE-2439
> URL: https://issues.apache.org/jira/browse/HIVE-2439
> Project: Hive
>  Issue Type: Improvement
>Affects Versions: 0.8.0
>Reporter: Ashutosh Chauhan
> Attachments: HIVE-2439_branch9_2.patch, HIVE-2439_branch9_3.patch, 
> HIVE-2439_branch9.patch, hive-2439_incomplete.patch
>
>
> Upgrade antlr version to 3.4

--
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 # 1840 - Still Failing

2012-12-07 Thread Apache Jenkins Server

Changes for Build #1831
[namit] HIVE-3747 Provide hive operation name for hookContext
(Shreepadma Venugopalan via namit)


Changes for Build #1832

Changes for Build #1833
[namit] HIVE-3750 JDBCStatsPublisher fails when ID length exceeds length of ID 
column
(Kevin Wilfong via namit)


Changes for Build #1835
[namit] HIVE-3073 Hive List Bucketing - DML support
(Gang Tim Liu via namit)

[namit] HIVE-3771 HIVE-3750 broke TestParse
(Kevin Wilfong via namit)

[hashutosh] HIVE-3384 : HIVE JDBC module won't compile under JDK1.7 as new 
methods added in JDBC specification (Shengsheng Huang, Chris Drome, Mikhail 
Bautin via Ashutosh Chauhan)

[namit] HIVE-3702 Renaming table changes table location scheme/authority
(Kevin Wilfong via namit)


Changes for Build #1836
[namit] HIVE-2723 should throw "Ambiguous column reference key" Exception in 
particular
join condition (Navis via namit)

[namit] HIVE-3594 When Group by Partition Column Type is Timestamp or STRING 
Which Format contains "HH:MM:SS",
It will occur URISyntaxException (Navis via namit)


Changes for Build #1837
[namit] HIVE-3762 Minor fix for 'tableName' in Hive.g
(Navis via namit)


Changes for Build #1838

Changes for Build #1839
[namit] HIVE-2477 Use name of original expression for name of CAST output
(Navis via namit)


Changes for Build #1840
[hashutosh] HIVE-3400 : Add Retries to Hive MetaStore Connections (Bhushan 
Mandhani via Ashutosh Chauhan)




1 tests failed.
FAILED:  org.apache.hadoop.hive.cli.TestCliDriver.testCliDriver_stats19

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.TestCliDriver.testCliDriver_stats19(TestCliDriver.java:41260)
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 #1840)

Status: Still Failing

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

[jira] [Commented] (HIVE-3400) Add Retries to Hive MetaStore Connections

2012-12-07 Thread Hudson (JIRA)


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

Hudson commented on HIVE-3400:
--

Integrated in Hive-trunk-h0.21 #1840 (See 
[https://builds.apache.org/job/Hive-trunk-h0.21/1840/])
HIVE-3400 : Add Retries to Hive MetaStore Connections (Bhushan Mandhani via 
Ashutosh Chauhan) (Revision 1418190)

 Result = FAILURE
hashutosh : 
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1418190
Files : 
* /hive/trunk/common/src/java/org/apache/hadoop/hive/conf/HiveConf.java
* /hive/trunk/conf/hive-default.xml.template
* 
/hive/trunk/metastore/src/java/org/apache/hadoop/hive/metastore/HiveMetaStoreClient.java
* 
/hive/trunk/metastore/src/java/org/apache/hadoop/hive/metastore/IMetaStoreClient.java
* 
/hive/trunk/metastore/src/java/org/apache/hadoop/hive/metastore/MetaStoreUtils.java
* 
/hive/trunk/metastore/src/java/org/apache/hadoop/hive/metastore/RetryingHMSHandler.java
* 
/hive/trunk/metastore/src/java/org/apache/hadoop/hive/metastore/RetryingMetaStoreClient.java
* 
/hive/trunk/metastore/src/java/org/apache/hadoop/hive/metastore/RetryingRawStore.java
* 
/hive/trunk/metastore/src/test/org/apache/hadoop/hive/metastore/TestMarkPartitionRemote.java
* 
/hive/trunk/metastore/src/test/org/apache/hadoop/hive/metastore/TestMetaStoreAuthorization.java
* 
/hive/trunk/metastore/src/test/org/apache/hadoop/hive/metastore/TestMetaStoreEndFunctionListener.java
* 
/hive/trunk/metastore/src/test/org/apache/hadoop/hive/metastore/TestMetaStoreEventListener.java
* /hive/trunk/ql/src/java/org/apache/hadoop/hive/ql/metadata/Hive.java


> Add Retries to Hive MetaStore Connections
> -
>
> Key: HIVE-3400
> URL: https://issues.apache.org/jira/browse/HIVE-3400
> Project: Hive
>  Issue Type: Improvement
>  Components: Metastore
>Reporter: Bhushan Mandhani
>Assignee: Bhushan Mandhani
>Priority: Minor
>  Labels: metastore
> Fix For: 0.10.0
>
> Attachments: HIVE-3400.1.patch.txt, HIVE-3400.2.patch.txt, 
> HIVE-3400.3.patch.txt
>
>
> Currently, when using Thrift to access the MetaStore, if the Thrift host 
> dies, there is no mechanism to reconnect to some other host even if the 
> MetaStore URIs variable in the Conf contains multiple hosts. Hive should 
> retry and reconnect rather than throwing a communication link error.

--
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-2812) Hive multi group by single reducer optimization fails when aggregation with no keys followed by query with no aggregations

2012-12-07 Thread Namit Jain (JIRA)


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

Namit Jain updated HIVE-2812:
-

Affects Version/s: (was: 0.9.0)
   Status: Open  (was: Patch Available)

Can you refresh this ? It has been very long since it was visited.

> Hive multi group by single reducer optimization fails when aggregation with 
> no keys followed by query with no aggregations
> --
>
> Key: HIVE-2812
> URL: https://issues.apache.org/jira/browse/HIVE-2812
> Project: Hive
>  Issue Type: Bug
>Reporter: Kevin Wilfong
>Assignee: Kevin Wilfong
> Attachments: ASF.LICENSE.NOT.GRANTED--HIVE-2812.D1821.1.patch
>
>
> In multi insert queries where one subquery involves an aggregation with no 
> distinct or group by keys and is followed by a query without any 
> aggregations, like the following, Hive will attempt to add a group by 
> operator for the query without aggregations, causing semantic analysis to 
> fail.
> FROM src
> INSERT OVERWRITE TABLE table1 SELECT count(*)
> INSERT OVERWRITE TABLE table2 SELECT key;

--
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-3140) Comment indenting is broken for "describe" in CLI

2012-12-07 Thread Zhenxiao Luo (JIRA)


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

Zhenxiao Luo updated HIVE-3140:
---

Status: Patch Available  (was: Open)

> Comment indenting is broken for "describe" in CLI
> -
>
> Key: HIVE-3140
> URL: https://issues.apache.org/jira/browse/HIVE-3140
> Project: Hive
>  Issue Type: Bug
>  Components: CLI
>Reporter: Xiaoxiao Hou
>Assignee: Zhenxiao Luo
>  Labels: patch
> Fix For: 0.10.0
>
> Attachments: HIVE-3140.1.patch.txt, HIVE-3140.2.patch.txt, 
> hive.3140.3.patch, HIVE-3140.3.patch.txt
>
>   Original Estimate: 72h
>  Remaining Estimate: 72h
>
> Just go into the CLI and type "describe [TABLE_NAME]". If a comment has 
> multiple lines, it is completely unreadable due to poor comment indenting. 
> For example:
> birthdayParam string 1 = comment1
> 2 = comment2
> 3 = comment3
> But it supposed to display as:
> birthdayParam string 1 = comment1
>  2 = comment2
>  3 = comment3
> Comments should be indented the same amount on each line, i.e., if the 
> comment starts at row k for the first line of the comment, it should be 
> indented by k on line 2.

--
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-3728) make optimizing multi-group by configurable

2012-12-07 Thread Namit Jain (JIRA)


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

Namit Jain updated HIVE-3728:
-

Status: Patch Available  (was: Open)

> make optimizing multi-group by configurable
> ---
>
> Key: HIVE-3728
> URL: https://issues.apache.org/jira/browse/HIVE-3728
> Project: Hive
>  Issue Type: Bug
>  Components: Query Processor
>Reporter: Namit Jain
>Assignee: Namit Jain
> Attachments: hive.3728.2.patch, hive.3728.3.patch
>
>
> This was done as part of https://issues.apache.org/jira/browse/HIVE-609.
> This should be configurable.

--
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-3140) Comment indenting is broken for "describe" in CLI

2012-12-07 Thread Zhenxiao Luo (JIRA)


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

Zhenxiao Luo updated HIVE-3140:
---

Attachment: HIVE-3140.3.patch.txt

> Comment indenting is broken for "describe" in CLI
> -
>
> Key: HIVE-3140
> URL: https://issues.apache.org/jira/browse/HIVE-3140
> Project: Hive
>  Issue Type: Bug
>  Components: CLI
>Reporter: Xiaoxiao Hou
>Assignee: Zhenxiao Luo
>  Labels: patch
> Fix For: 0.10.0
>
> Attachments: HIVE-3140.1.patch.txt, HIVE-3140.2.patch.txt, 
> hive.3140.3.patch, HIVE-3140.3.patch.txt
>
>   Original Estimate: 72h
>  Remaining Estimate: 72h
>
> Just go into the CLI and type "describe [TABLE_NAME]". If a comment has 
> multiple lines, it is completely unreadable due to poor comment indenting. 
> For example:
> birthdayParam string 1 = comment1
> 2 = comment2
> 3 = comment3
> But it supposed to display as:
> birthdayParam string 1 = comment1
>  2 = comment2
>  3 = comment3
> Comments should be indented the same amount on each line, i.e., if the 
> comment starts at row k for the first line of the comment, it should be 
> indented by k on line 2.

--
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-3140) Comment indenting is broken for "describe" in CLI

2012-12-07 Thread Zhenxiao Luo (JIRA)


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

Zhenxiao Luo commented on HIVE-3140:


Updated and fixed the failing testcases, which fail due to the result format 
change of "describe TABLE_NAME".
Review request submitted at:
https://reviews.facebook.net/D7173

> Comment indenting is broken for "describe" in CLI
> -
>
> Key: HIVE-3140
> URL: https://issues.apache.org/jira/browse/HIVE-3140
> Project: Hive
>  Issue Type: Bug
>  Components: CLI
>Reporter: Xiaoxiao Hou
>Assignee: Zhenxiao Luo
>  Labels: patch
> Fix For: 0.10.0
>
> Attachments: HIVE-3140.1.patch.txt, HIVE-3140.2.patch.txt, 
> hive.3140.3.patch
>
>   Original Estimate: 72h
>  Remaining Estimate: 72h
>
> Just go into the CLI and type "describe [TABLE_NAME]". If a comment has 
> multiple lines, it is completely unreadable due to poor comment indenting. 
> For example:
> birthdayParam string 1 = comment1
> 2 = comment2
> 3 = comment3
> But it supposed to display as:
> birthdayParam string 1 = comment1
>  2 = comment2
>  3 = comment3
> Comments should be indented the same amount on each line, i.e., if the 
> comment starts at row k for the first line of the comment, it should be 
> indented by k on line 2.

--
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-3767) BucketizedHiveInputFormat should be automatically used with Bucketized Map Joins also

2012-12-07 Thread Namit Jain (JIRA)


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

Namit Jain updated HIVE-3767:
-

  Resolution: Fixed
Hadoop Flags: Reviewed
  Status: Resolved  (was: Patch Available)

Committed. Thanks Tim

> BucketizedHiveInputFormat should be automatically used with Bucketized Map 
> Joins also
> -
>
> Key: HIVE-3767
> URL: https://issues.apache.org/jira/browse/HIVE-3767
> Project: Hive
>  Issue Type: Bug
>  Components: Query Processor
>Reporter: Namit Jain
>Assignee: Gang Tim Liu
> Attachments: HIVE-3767.patch.2
>
>
> It seems like even after https://issues.apache.org/jira/browse/HIVE-3219 we 
> still need to set hive.input.format = 
> org.apache.hadoop.hive.ql.io.BucketizedHiveInputFormat for bucket map joins 
> (though not SMB joins)

--
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-3084) Hive CI failing due to script_broken_pipe1.q

2012-12-07 Thread Gunther Hagleitner (JIRA)


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

Gunther Hagleitner updated HIVE-3084:
-

Status: Patch Available  (was: Open)

> Hive CI failing due to script_broken_pipe1.q
> 
>
> Key: HIVE-3084
> URL: https://issues.apache.org/jira/browse/HIVE-3084
> Project: Hive
>  Issue Type: Bug
>Reporter: Travis Crawford
>Assignee: Gunther Hagleitner
> Attachments: HIVE-3084_disable_failing_test.1.patch, 
> HIVE-3084_two_script_operators.patch
>
>
> Hive's [CI job|https://builds.apache.org/job/Hive-trunk-h0.21/] regularly 
> fails due to this test:
> {code}
> org.apache.hadoop.hive.cli.TestNegativeCliDriver.testNegativeCliDriver_script_broken_pipe1
> {code}
> Running just that test in a loop I'm not able to reproduce the issue locally. 
> This may be related to state from a previous test causing this one to fail?
> {code}
> ant clean package
> for x in $(seq 1 10); 
>   do ant test -Dtestcase=TestNegativeCliDriver -Dqfile=script_broken_pipe1.q;
> done
> {code}

--
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] [Assigned] (HIVE-3084) Hive CI failing due to script_broken_pipe1.q

2012-12-07 Thread Gunther Hagleitner (JIRA)


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

Gunther Hagleitner reassigned HIVE-3084:


Assignee: Gunther Hagleitner  (was: Travis Crawford)

> Hive CI failing due to script_broken_pipe1.q
> 
>
> Key: HIVE-3084
> URL: https://issues.apache.org/jira/browse/HIVE-3084
> Project: Hive
>  Issue Type: Bug
>Reporter: Travis Crawford
>Assignee: Gunther Hagleitner
> Attachments: HIVE-3084_disable_failing_test.1.patch, 
> HIVE-3084_two_script_operators.patch
>
>
> Hive's [CI job|https://builds.apache.org/job/Hive-trunk-h0.21/] regularly 
> fails due to this test:
> {code}
> org.apache.hadoop.hive.cli.TestNegativeCliDriver.testNegativeCliDriver_script_broken_pipe1
> {code}
> Running just that test in a loop I'm not able to reproduce the issue locally. 
> This may be related to state from a previous test causing this one to fail?
> {code}
> ant clean package
> for x in $(seq 1 10); 
>   do ant test -Dtestcase=TestNegativeCliDriver -Dqfile=script_broken_pipe1.q;
> done
> {code}

--
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-3084) Hive CI failing due to script_broken_pipe1.q

2012-12-07 Thread Gunther Hagleitner (JIRA)


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

Gunther Hagleitner updated HIVE-3084:
-

Attachment: HIVE-3084_two_script_operators.patch

> Hive CI failing due to script_broken_pipe1.q
> 
>
> Key: HIVE-3084
> URL: https://issues.apache.org/jira/browse/HIVE-3084
> Project: Hive
>  Issue Type: Bug
>Reporter: Travis Crawford
>Assignee: Gunther Hagleitner
> Attachments: HIVE-3084_disable_failing_test.1.patch, 
> HIVE-3084_two_script_operators.patch
>
>
> Hive's [CI job|https://builds.apache.org/job/Hive-trunk-h0.21/] regularly 
> fails due to this test:
> {code}
> org.apache.hadoop.hive.cli.TestNegativeCliDriver.testNegativeCliDriver_script_broken_pipe1
> {code}
> Running just that test in a loop I'm not able to reproduce the issue locally. 
> This may be related to state from a previous test causing this one to fail?
> {code}
> ant clean package
> for x in $(seq 1 10); 
>   do ant test -Dtestcase=TestNegativeCliDriver -Dqfile=script_broken_pipe1.q;
> done
> {code}

--
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-3084) Hive CI failing due to script_broken_pipe1.q

2012-12-07 Thread Gunther Hagleitner (JIRA)


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

Gunther Hagleitner commented on HIVE-3084:
--

I ran into the same issue. It affects both script_broken_pipe1.q as well as 
minimr_broken_pipe.q. script_broken_pipe3.q has the same problem, but it won't 
cause the test to fail - just to not test what it was intended to do.

The test seems to assume that the user process (bash's "true") exits and closes 
its stdin before the ScriptOperator closes the associated output (in the close 
method). There is however no guarantee that things happen in this sequence and 
if they don't there will be no exception thrown.

I have rewritten the tests using two ScriptOperators in the pipeline. The first 
one will exit properly, the second one will throw the exception. Closing the 
first ScriptOperator (flushing buffers, waitFor...) should ensure that the 
second user process had a chance to exit, although strictly speaking there is 
still no guarantee. I've run this a number of time and wasn't able to reproduce 
the issue with the fix. 

> Hive CI failing due to script_broken_pipe1.q
> 
>
> Key: HIVE-3084
> URL: https://issues.apache.org/jira/browse/HIVE-3084
> Project: Hive
>  Issue Type: Bug
>Reporter: Travis Crawford
>Assignee: Travis Crawford
> Attachments: HIVE-3084_disable_failing_test.1.patch, 
> HIVE-3084_two_script_operators.patch
>
>
> Hive's [CI job|https://builds.apache.org/job/Hive-trunk-h0.21/] regularly 
> fails due to this test:
> {code}
> org.apache.hadoop.hive.cli.TestNegativeCliDriver.testNegativeCliDriver_script_broken_pipe1
> {code}
> Running just that test in a loop I'm not able to reproduce the issue locally. 
> This may be related to state from a previous test causing this one to fail?
> {code}
> ant clean package
> for x in $(seq 1 10); 
>   do ant test -Dtestcase=TestNegativeCliDriver -Dqfile=script_broken_pipe1.q;
> done
> {code}

--
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-3779) An empty value to hive.logquery.location can't disable the creation of hive history log files

2012-12-07 Thread Bing Li (JIRA)

Bing Li created HIVE-3779:
-

 Summary: An empty value to hive.logquery.location can't disable 
the creation of hive history log files
 Key: HIVE-3779
 URL: https://issues.apache.org/jira/browse/HIVE-3779
 Project: Hive
  Issue Type: Bug
  Components: Documentation
Affects Versions: 0.9.0
Reporter: Bing Li
Priority: Minor


In AdminManual Configuration 
(https://cwiki.apache.org/Hive/adminmanual-configuration.html), the description 
of hive.querylog.location mentioned that if the variable set to empty string 
structured log will not be created.

But it fails with the following setting,

  hive.querylog.location
   


It seems that it can NOT get an empty value from 
HiveConf.ConfVars.HIVEHISTORYFILELOC, but the default value.

--
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-2918) Hive Dynamic Partition Insert - move task not considering 'hive.exec.max.dynamic.partitions' from CLI

2012-12-07 Thread hordaway (JIRA)


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

hordaway commented on HIVE-2918:


超过默认值1000了，重新设置以后不生效，是因为conf没有生效，可找到hive.java这个文件进行修改

> Hive Dynamic Partition Insert - move task not considering 
> 'hive.exec.max.dynamic.partitions' from CLI
> -
>
> Key: HIVE-2918
> URL: https://issues.apache.org/jira/browse/HIVE-2918
> Project: Hive
>  Issue Type: Bug
>Affects Versions: 0.7.1, 0.8.0, 0.8.1, 0.9.0
> Environment: Cent OS 64 bit
>Reporter: Bejoy KS
>Assignee: Carl Steinbach
> Fix For: 0.10.0
>
> Attachments: ASF.LICENSE.NOT.GRANTED--HIVE-2918.D2703.1.patch
>
>
> Dynamic Partition insert showing an error with the number of partitions 
> created even after the default value of 'hive.exec.max.dynamic.partitions' is 
> bumped high to 2000.
> Error Message:
> "Failed with exception Number of dynamic partitions created is 1413, which is 
> more than 1000. To solve this try to set hive.exec.max.dynamic.partitions to 
> at least 1413."
> These are the following properties set on hive CLI
> hive> set hive.exec.dynamic.partition=true;
> hive> set hive.exec.dynamic.partition.mode=nonstrict;
> hive> set hive.exec.max.dynamic.partitions=2000;
> hive> set hive.exec.max.dynamic.partitions.pernode=2000;
> This is the query with console error log
> hive> 
> > INSERT OVERWRITE TABLE partn_dyn Partition (pobox)
> > SELECT country,state,pobox FROM non_partn_dyn;
> Total MapReduce jobs = 2
> Launching Job 1 out of 2
> Number of reduce tasks is set to 0 since there's no reduce operator
> Starting Job = job_201204021529_0002, Tracking URL = 
> http://0.0.0.0:50030/jobdetails.jsp?jobid=job_201204021529_0002
> Kill Command = /usr/lib/hadoop/bin/hadoop job  
> -Dmapred.job.tracker=0.0.0.0:8021 -kill job_201204021529_0002
> 2012-04-02 16:05:28,619 Stage-1 map = 0%,  reduce = 0%
> 2012-04-02 16:05:39,701 Stage-1 map = 100%,  reduce = 0%
> 2012-04-02 16:05:50,800 Stage-1 map = 100%,  reduce = 100%
> Ended Job = job_201204021529_0002
> Ended Job = 248865587, job is filtered out (removed at runtime).
> Moving data to: 
> hdfs://0.0.0.0/tmp/hive-cloudera/hive_2012-04-02_16-05-24_919_5976014408587784412/-ext-1
> Loading data to table default.partn_dyn partition (pobox=null)
> Failed with exception Number of dynamic partitions created is 1413, which is 
> more than 1000. To solve this try to set hive.exec.max.dynamic.partitions to 
> at least 1413.
> FAILED: Execution Error, return code 1 from 
> org.apache.hadoop.hive.ql.exec.MoveTask
> I checked the job.xml of the first map only job, there the value 
> hive.exec.max.dynamic.partitions=2000 is reflected but the move task is 
> taking the default value from hive-site.xml . If I change the value in 
> hive-site.xml then the job completes successfully. Bottom line,the property 
> 'hive.exec.max.dynamic.partitions'set on CLI is not being considered by move 
> task

--
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-3760) TestNegativeMinimrCliDriver_mapreduce_stack_trace.q fails on hadoop-1

2012-12-07 Thread Zhenxiao Luo (JIRA)


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

Zhenxiao Luo commented on HIVE-3760:


Hi, [~ashutoshc] and [~hagleitn]:
I'd like to say that this is my fault. I did not set the configuration 
correctly when doing the EXCLUDE/INCLUDE versions. Sorry about that, and thanks 
a lot for the fix.

Zhenixao

> TestNegativeMinimrCliDriver_mapreduce_stack_trace.q fails on hadoop-1
> -
>
> Key: HIVE-3760
> URL: https://issues.apache.org/jira/browse/HIVE-3760
> Project: Hive
>  Issue Type: Bug
>Reporter: Ashutosh Chauhan
>Assignee: Gunther Hagleitner
> Attachments: HIVE-3760.2.patch, hive-3760.patch
>
>
> Actually functionality is working correctly, but incorrect include/exclude 
> macro in test directive is making its .q.out comparison against incorrect 
> results.

--
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-3760) TestNegativeMinimrCliDriver_mapreduce_stack_trace.q fails on hadoop-1

2012-12-07 Thread Gunther Hagleitner (JIRA)


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

Gunther Hagleitner updated HIVE-3760:
-

Status: Patch Available  (was: Open)

> TestNegativeMinimrCliDriver_mapreduce_stack_trace.q fails on hadoop-1
> -
>
> Key: HIVE-3760
> URL: https://issues.apache.org/jira/browse/HIVE-3760
> Project: Hive
>  Issue Type: Bug
>Reporter: Ashutosh Chauhan
>Assignee: Gunther Hagleitner
> Attachments: HIVE-3760.2.patch, hive-3760.patch
>
>
> Actually functionality is working correctly, but incorrect include/exclude 
> macro in test directive is making its .q.out comparison against incorrect 
> results.

--
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-3760) TestNegativeMinimrCliDriver_mapreduce_stack_trace.q fails on hadoop-1

2012-12-07 Thread Gunther Hagleitner (JIRA)


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

Gunther Hagleitner updated HIVE-3760:
-

Attachment: HIVE-3760.2.patch

> TestNegativeMinimrCliDriver_mapreduce_stack_trace.q fails on hadoop-1
> -
>
> Key: HIVE-3760
> URL: https://issues.apache.org/jira/browse/HIVE-3760
> Project: Hive
>  Issue Type: Bug
>Reporter: Ashutosh Chauhan
>Assignee: Gunther Hagleitner
> Attachments: HIVE-3760.2.patch, hive-3760.patch
>
>
> Actually functionality is working correctly, but incorrect include/exclude 
> macro in test directive is making its .q.out comparison against incorrect 
> results.

--
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-3760) TestNegativeMinimrCliDriver_mapreduce_stack_trace.q fails on hadoop-1

2012-12-07 Thread Gunther Hagleitner (JIRA)


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

Gunther Hagleitner commented on HIVE-3760:
--

The mapreduce_stack_trace_turnoff test is also misconfigured. Applied the same 
fix to both in the second patch.

> TestNegativeMinimrCliDriver_mapreduce_stack_trace.q fails on hadoop-1
> -
>
> Key: HIVE-3760
> URL: https://issues.apache.org/jira/browse/HIVE-3760
> Project: Hive
>  Issue Type: Bug
>Reporter: Ashutosh Chauhan
>Assignee: Gunther Hagleitner
> Attachments: HIVE-3760.2.patch, hive-3760.patch
>
>
> Actually functionality is working correctly, but incorrect include/exclude 
> macro in test directive is making its .q.out comparison against incorrect 
> results.

--
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-3760) TestNegativeMinimrCliDriver_mapreduce_stack_trace.q fails on hadoop-1

2012-12-07 Thread Gunther Hagleitner (JIRA)


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

Gunther Hagleitner updated HIVE-3760:
-

Assignee: Gunther Hagleitner  (was: Ashutosh Chauhan)

> TestNegativeMinimrCliDriver_mapreduce_stack_trace.q fails on hadoop-1
> -
>
> Key: HIVE-3760
> URL: https://issues.apache.org/jira/browse/HIVE-3760
> Project: Hive
>  Issue Type: Bug
>Reporter: Ashutosh Chauhan
>Assignee: Gunther Hagleitner
> Attachments: hive-3760.patch
>
>
> Actually functionality is working correctly, but incorrect include/exclude 
> macro in test directive is making its .q.out comparison against incorrect 
> results.

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

Re: Review request: JIRAs useful for the Shark project

2012-12-07 Thread Mikhail Bautin

Thanks a lot to Ashutosh for reviewing and committing HIVE-3384 to trunk.
We still have the following patches outstanding that would help the Shark
project a lot -- your feedback / reviewing / committing would be much
appreciated!

   - https://reviews.facebook.net/D6879
(HIVE-3731):
   adding an Ant target to create a Debian package, which allows deploying the
   patched version of Hive alongside Shark on Debian systems.
   - https://reviews.facebook.net/D7155
(HIVE-3772):
   a one-line concurrency bug fix in LazyBinaryUtils (patch by Reynold Xin).

Thanks,
Mikhail


On Tue, Nov 27, 2012 at 7:08 PM, Ashutosh Chauhan wrote:

> Hi Mikhail,
>
> I will take a look into those jiras.
>
> Thanks,
> Ashutosh
>
> On Tue, Nov 27, 2012 at 11:43 AM, Mikhail Bautin <
> bautin.mailing.li...@gmail.com> wrote:
>
> > Hello,
> >
> > There are the following review requests pending that are very useful for
> > the Shark project (http://shark.cs.berkeley.edu/). It would be great if
> > someone could take a look and help us get these JIRAs committed.
> >
> >- https://reviews.facebook.net/D6879
> > (HIVE-3731):
> >adding an Ant target to create a Debian package, which allows
> deploying
> > the
> >patched version of Hive alongside Shark on Debian systems.
> >- https://reviews.facebook.net/D7005
> > (HIVE-3748):
> >making QTestUtil work correctly when running the test suite, which
> helps
> >with running Hive/Shark unit tests from using Maven.
> >
> > In addition, the following JIRA would make a lot easier to work with Hive
> > for anyone who is using JDK 1.7:
> >
> >- https://reviews.facebook.net/D6873
> > (HIVE-3384):
> >HIVE JDBC module won't compile under JDK1.7 as new methods added in
> JDBC
> >specification
> >
> > Your help in reviewing/committing these patches is greatly appreciated!
> >
> > Thanks,
> > Mikhail
> >
>

59 matches

Mail list logo