[jira] [Updated] (HIVE-11750) ODBC Driver returns column names prefixed with table name

2015-09-07 Thread Stefan (JIRA) 

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

Stefan updated HIVE-11750:
--
Description: 
I created two tables, e.g.
  1.) create table t1 (abc int comment 'test column') PARTITIONED BY (abc2 
string comment '');
  2.) create table t2 (abc int comment 'test column');

For table t1 the odbc driver returns a table with column names 't1.abc' and 
't1.abc2'. Notice the table prefix, which causes problems in some aplications.

For table t2 the odbc driver returns a table with column names 'abc', which is 
ok.

It seems that the partitioned by is causing some problems to the ODBC driver.


  was:
I created two tables, e.g.
  1.) create table t1 (abc int comment 'test column') PARTITIONED BY (abc2 
string comment '');
  2.) create table t2 (abc int comment 'test column');

For table t1 the odbc driver returns a table with column names 't1.abc' and 
't1.abc2'. Notice the table prefix, which causes problems in some aplications.

For table t2 the odbc driver returns a table with column names 'abc', which is 
ok.

It seems that the partitioned by is causing some problems to JDBC driver.



> ODBC Driver returns column names prefixed with table name
> -
>
> Key: HIVE-11750
> URL: https://issues.apache.org/jira/browse/HIVE-11750
> Project: Hive
>  Issue Type: Bug
>Reporter: Stefan
>
> I created two tables, e.g.
>   1.) create table t1 (abc int comment 'test column') PARTITIONED BY (abc2 
> string comment '');
>   2.) create table t2 (abc int comment 'test column');
> For table t1 the odbc driver returns a table with column names 't1.abc' and 
> 't1.abc2'. Notice the table prefix, which causes problems in some aplications.
> For table t2 the odbc driver returns a table with column names 'abc', which 
> is ok.
> It seems that the partitioned by is causing some problems to the ODBC driver.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (HIVE-11748) HivePreparedStatement's setTimestamp() does not quote value as required

2015-09-07 Thread Hive QA (JIRA) 

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

Hive QA commented on HIVE-11748:




{color:red}Overall{color}: -1 at least one tests failed

Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12754494/HIVE-11748.2.patch

{color:red}ERROR:{color} -1 due to 1 failed/errored test(s), 9421 tests executed
*Failed tests:*
{noformat}
org.apache.hive.hcatalog.api.TestHCatClient.testTableSchemaPropagation
{noformat}

Test results: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/5191/testReport
Console output: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/5191/console
Test logs: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/logs/PreCommit-HIVE-TRUNK-Build-5191/

Messages:
{noformat}
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
Tests exited with: TestsFailedException: 1 tests failed
{noformat}

This message is automatically generated.

ATTACHMENT ID: 12754494 - PreCommit-HIVE-TRUNK-Build

> HivePreparedStatement's setTimestamp() does not quote value as required
> ---
>
> Key: HIVE-11748
> URL: https://issues.apache.org/jira/browse/HIVE-11748
> Project: Hive
>  Issue Type: Bug
>  Components: JDBC
>Reporter: Angus Smithson
> Attachments: HIVE-11748.2.patch, HIVE-11748.patch
>
>
> [HivePreparedStatement.setTimestamp(int parameterIndex, Timestamp 
> x)|https://hive.apache.org/javadocs/r1.2.1/api/org/apache/hive/jdbc/HivePreparedStatement.html#setTimestamp(int,%20java.sql.Timestamp)]
>  does not quote the Timestamp value when generating the HQL statement, 
> resulting in a HiveSqlException on execution.
> h5. Reproducing
> If we add the following unit test to 
> {{itests/hive-unit/src/test/java/org/apache/hive/jdbc/TestJdbcDriver2.java}}:
> {code}
>   @Test
>   public void testPrepareSetTimestamp() throws SQLException, ParseException {
> String sql = String.format("SELECT * FROM %s WHERE c20 = ?", 
> dataTypeTableName);
> try (PreparedStatement ps = con.prepareStatement(sql)) {
>   Timestamp timestamp = new Timestamp(new 
> SimpleDateFormat("-MM-dd").parse("2013-01-01").getTime());
>   ps.setTimestamp(1, timestamp);
>   try (ResultSet resultSet = ps.executeQuery()) {
> assertTrue(resultSet.next());
> assertEquals("2013-01-01", resultSet.getString(20));
>   }
> }
>   }
> {code}
> The test fails:
> {noformat}
> org.apache.hive.service.cli.HiveSQLException: Error while compiling 
> statement: FAILED: ParseException line 1:55 cannot recognize input near '00' 
> ':' '00' in expression specification
>   at org.apache.hadoop.hive.ql.parse.ParseDriver.parse(ParseDriver.java:205)
>   at org.apache.hadoop.hive.ql.parse.ParseDriver.parse(ParseDriver.java:166)
>   at org.apache.hadoop.hive.ql.Driver.compile(Driver.java:401)
>   at org.apache.hadoop.hive.ql.Driver.compile(Driver.java:310)
>   at org.apache.hadoop.hive.ql.Driver.compileInternal(Driver.java:1150)
>   at org.apache.hadoop.hive.ql.Driver.compileAndRespond(Driver.java:1136)
>   at 
> org.apache.hive.service.cli.operation.SQLOperation.prepare(SQLOperation.java:109)
>   at 
> org.apache.hive.service.cli.operation.SQLOperation.runInternal(SQLOperation.java:180)
>   at 
> org.apache.hive.service.cli.operation.Operation.run(Operation.java:257)
>   at 
> org.apache.hive.service.cli.session.HiveSessionImpl.executeStatementInternal(HiveSessionImpl.java:405)
>   at 
> org.apache.hive.service.cli.session.HiveSessionImpl.executeStatementAsync(HiveSessionImpl.java:392)
>   at 
> org.apache.hive.service.cli.CLIService.executeStatementAsync(CLIService.java:261)
>   at 
> org.apache.hive.service.cli.thrift.ThriftCLIService.ExecuteStatement(ThriftCLIService.java:509)
>   at sun.reflect.GeneratedMethodAccessor15.invoke(Unknown Source)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:606)
>   at 
> org.apache.hive.jdbc.HiveConnection$SynchronizedHandler.invoke(HiveConnection.java:1400)
>   at com.sun.proxy.$Proxy32.ExecuteStatement(Unknown Source)
>   at org.apache.hive.jdbc.HiveStatement.execute(HiveStatement.java:246)
>   at 
> org.apache.hive.jdbc.HiveStatement.executeQuery(HiveStatement.java:378)
>   at 
> org.apache.hive.jdbc.HivePreparedStatement.executeQuery(HivePreparedStatement.java:109)
>   at 
> org.apache.hive.jdbc.TestJdbcDriver2.testPrepareSetTimestamp(TestJdbcDriver2.java:2395)
> {noformat}
> The failure is

[jira] [Updated] (HIVE-11748) HivePreparedStatement's setTimestamp() does not quote value as required

2015-09-07 Thread Angus Smithson (JIRA) 

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

Angus Smithson updated HIVE-11748:
--
Attachment: HIVE-11748.2.patch

Attaching HIVE-11748.2.patch.
 - Added support for Timestamp to HivePreparedStatement.setObject(int 
parameterIndex, Object x)
 - Added coverage of setTimestamp() and setObject(Timestamp x) to 
TestJdbcDriver2.testPrepareStatement()
 - General tidy-up of TestJdbcDriver2.testPrepareStatement()
 -- fixed resource leaks
 -- made useful (it was incorrectly passing even if no results returned!)
 - Rewrote TestJdbcDriver2·testPrepareSetTimestamp() to use Timestamp objects 
rather than Date.

\\

I suggest someone with edit privileges on 
https://cwiki.apache.org/confluence/display/Hive/HowToContribute changes the 
[unit 
tests|https://cwiki.apache.org/confluence/display/Hive/HowToContribute#HowToContribute-UnitTests]
 section.  It's confusing for new contributors.  Currently it reads:
{noformat}
> cd hive-trunk
> mvn clean install -DskipTests -Phadoop-1
> mvn test -Dtest=SomeTest -Phadoop-1
{noformat}

There isn't a "hive-trunk" anymore.  I think\* the correct procedure is:
{noformat}
mvn clean install -DskipTests -Phadoop-1
cd itests
mvn test -Dtest=SomeTest -Phadoop-1
{noformat}
_\* This is how I executed TestJdbcDriver2 locally - please comment if there's 
a better way_

> HivePreparedStatement's setTimestamp() does not quote value as required
> ---
>
> Key: HIVE-11748
> URL: https://issues.apache.org/jira/browse/HIVE-11748
> Project: Hive
>  Issue Type: Bug
>  Components: JDBC
>Reporter: Angus Smithson
>Assignee: Angus Smithson
> Attachments: HIVE-11748.2.patch, HIVE-11748.patch
>
>
> [HivePreparedStatement.setTimestamp(int parameterIndex, Timestamp 
> x)|https://hive.apache.org/javadocs/r1.2.1/api/org/apache/hive/jdbc/HivePreparedStatement.html#setTimestamp(int,%20java.sql.Timestamp)]
>  does not quote the Timestamp value when generating the HQL statement, 
> resulting in a HiveSqlException on execution.
> h5. Reproducing
> If we add the following unit test to 
> {{itests/hive-unit/src/test/java/org/apache/hive/jdbc/TestJdbcDriver2.java}}:
> {code}
>   @Test
>   public void testPrepareSetTimestamp() throws SQLException, ParseException {
> String sql = String.format("SELECT * FROM %s WHERE c20 = ?", 
> dataTypeTableName);
> try (PreparedStatement ps = con.prepareStatement(sql)) {
>   Timestamp timestamp = new Timestamp(new 
> SimpleDateFormat("-MM-dd").parse("2013-01-01").getTime());
>   ps.setTimestamp(1, timestamp);
>   try (ResultSet resultSet = ps.executeQuery()) {
> assertTrue(resultSet.next());
> assertEquals("2013-01-01", resultSet.getString(20));
>   }
> }
>   }
> {code}
> The test fails:
> {noformat}
> org.apache.hive.service.cli.HiveSQLException: Error while compiling 
> statement: FAILED: ParseException line 1:55 cannot recognize input near '00' 
> ':' '00' in expression specification
>   at org.apache.hadoop.hive.ql.parse.ParseDriver.parse(ParseDriver.java:205)
>   at org.apache.hadoop.hive.ql.parse.ParseDriver.parse(ParseDriver.java:166)
>   at org.apache.hadoop.hive.ql.Driver.compile(Driver.java:401)
>   at org.apache.hadoop.hive.ql.Driver.compile(Driver.java:310)
>   at org.apache.hadoop.hive.ql.Driver.compileInternal(Driver.java:1150)
>   at org.apache.hadoop.hive.ql.Driver.compileAndRespond(Driver.java:1136)
>   at 
> org.apache.hive.service.cli.operation.SQLOperation.prepare(SQLOperation.java:109)
>   at 
> org.apache.hive.service.cli.operation.SQLOperation.runInternal(SQLOperation.java:180)
>   at 
> org.apache.hive.service.cli.operation.Operation.run(Operation.java:257)
>   at 
> org.apache.hive.service.cli.session.HiveSessionImpl.executeStatementInternal(HiveSessionImpl.java:405)
>   at 
> org.apache.hive.service.cli.session.HiveSessionImpl.executeStatementAsync(HiveSessionImpl.java:392)
>   at 
> org.apache.hive.service.cli.CLIService.executeStatementAsync(CLIService.java:261)
>   at 
> org.apache.hive.service.cli.thrift.ThriftCLIService.ExecuteStatement(ThriftCLIService.java:509)
>   at sun.reflect.GeneratedMethodAccessor15.invoke(Unknown Source)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:606)
>   at 
> org.apache.hive.jdbc.HiveConnection$SynchronizedHandler.invoke(HiveConnection.java:1400)
>   at com.sun.proxy.$Proxy32.ExecuteStatement(Unknown Source)
>   at org.apache.hive.jdbc.HiveStatement.execute(HiveStatement.java:246)
>   at 
> org.apache.hive.jdbc.HiveStatement.executeQuery(HiveStatement.java:378)
>   at 
>

[jira] [Commented] (HIVE-11329) Column prefix in key of hbase column prefix map

2015-09-07 Thread Wojciech Indyk (JIRA) 

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

Wojciech Indyk commented on HIVE-11329:
---

[~spena], what we need to do to commit this patch?

> Column prefix in key of hbase column prefix map
> ---
>
> Key: HIVE-11329
> URL: https://issues.apache.org/jira/browse/HIVE-11329
> Project: Hive
>  Issue Type: Improvement
>  Components: HBase Handler
>Affects Versions: 0.14.0
>Reporter: Wojciech Indyk
>Assignee: Wojciech Indyk
>Priority: Minor
> Attachments: HIVE-11329.3.patch
>
>
> When I create a table with hbase column prefix 
> https://issues.apache.org/jira/browse/HIVE-3725 I have the prefix in result 
> map in hive. 
> E.g. record in HBase
> rowkey: 123
> column: tag_one, value: 0.5
> column: tag_two, value 0.5
> representation in Hive via column prefix mapping "tag_.*":
> column: tag map
> key: tag_one, value: 0.5
> key: tag_two, value: 0.5
> should be:
> key: one, value: 0.5
> key: two: value: 0.5



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (HIVE-11748) HivePreparedStatement's setTimestamp() does not quote value as required

2015-09-07 Thread Angus Smithson (JIRA) 

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

Angus Smithson commented on HIVE-11748:
---

The {{org.apache.hive.hcatalog.api.TestHCatClient.testTableSchemaPropagation}} 
test failure is unrelated, it was failing prior to my changes.

> HivePreparedStatement's setTimestamp() does not quote value as required
> ---
>
> Key: HIVE-11748
> URL: https://issues.apache.org/jira/browse/HIVE-11748
> Project: Hive
>  Issue Type: Bug
>  Components: JDBC
>Reporter: Angus Smithson
> Attachments: HIVE-11748.2.patch, HIVE-11748.patch
>
>
> [HivePreparedStatement.setTimestamp(int parameterIndex, Timestamp 
> x)|https://hive.apache.org/javadocs/r1.2.1/api/org/apache/hive/jdbc/HivePreparedStatement.html#setTimestamp(int,%20java.sql.Timestamp)]
>  does not quote the Timestamp value when generating the HQL statement, 
> resulting in a HiveSqlException on execution.
> h5. Reproducing
> If we add the following unit test to 
> {{itests/hive-unit/src/test/java/org/apache/hive/jdbc/TestJdbcDriver2.java}}:
> {code}
>   @Test
>   public void testPrepareSetTimestamp() throws SQLException, ParseException {
> String sql = String.format("SELECT * FROM %s WHERE c20 = ?", 
> dataTypeTableName);
> try (PreparedStatement ps = con.prepareStatement(sql)) {
>   Timestamp timestamp = new Timestamp(new 
> SimpleDateFormat("-MM-dd").parse("2013-01-01").getTime());
>   ps.setTimestamp(1, timestamp);
>   try (ResultSet resultSet = ps.executeQuery()) {
> assertTrue(resultSet.next());
> assertEquals("2013-01-01", resultSet.getString(20));
>   }
> }
>   }
> {code}
> The test fails:
> {noformat}
> org.apache.hive.service.cli.HiveSQLException: Error while compiling 
> statement: FAILED: ParseException line 1:55 cannot recognize input near '00' 
> ':' '00' in expression specification
>   at org.apache.hadoop.hive.ql.parse.ParseDriver.parse(ParseDriver.java:205)
>   at org.apache.hadoop.hive.ql.parse.ParseDriver.parse(ParseDriver.java:166)
>   at org.apache.hadoop.hive.ql.Driver.compile(Driver.java:401)
>   at org.apache.hadoop.hive.ql.Driver.compile(Driver.java:310)
>   at org.apache.hadoop.hive.ql.Driver.compileInternal(Driver.java:1150)
>   at org.apache.hadoop.hive.ql.Driver.compileAndRespond(Driver.java:1136)
>   at 
> org.apache.hive.service.cli.operation.SQLOperation.prepare(SQLOperation.java:109)
>   at 
> org.apache.hive.service.cli.operation.SQLOperation.runInternal(SQLOperation.java:180)
>   at 
> org.apache.hive.service.cli.operation.Operation.run(Operation.java:257)
>   at 
> org.apache.hive.service.cli.session.HiveSessionImpl.executeStatementInternal(HiveSessionImpl.java:405)
>   at 
> org.apache.hive.service.cli.session.HiveSessionImpl.executeStatementAsync(HiveSessionImpl.java:392)
>   at 
> org.apache.hive.service.cli.CLIService.executeStatementAsync(CLIService.java:261)
>   at 
> org.apache.hive.service.cli.thrift.ThriftCLIService.ExecuteStatement(ThriftCLIService.java:509)
>   at sun.reflect.GeneratedMethodAccessor15.invoke(Unknown Source)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:606)
>   at 
> org.apache.hive.jdbc.HiveConnection$SynchronizedHandler.invoke(HiveConnection.java:1400)
>   at com.sun.proxy.$Proxy32.ExecuteStatement(Unknown Source)
>   at org.apache.hive.jdbc.HiveStatement.execute(HiveStatement.java:246)
>   at 
> org.apache.hive.jdbc.HiveStatement.executeQuery(HiveStatement.java:378)
>   at 
> org.apache.hive.jdbc.HivePreparedStatement.executeQuery(HivePreparedStatement.java:109)
>   at 
> org.apache.hive.jdbc.TestJdbcDriver2.testPrepareSetTimestamp(TestJdbcDriver2.java:2395)
> {noformat}
> The failure is because the following HQL is generated/executed by calling 
> toString() on the Timestamp value:
> {noformat}
> SELECT * FROM testdatatypetable WHERE c20 = 2013-01-01 00:00:00.0
> {noformat}
> We should be quoting the value of Timestamp.toString(), so that the following 
> HQL is generated/executed:
> {noformat}
> SELECT * FROM testdatatypetable WHERE c20 = '2013-01-01 00:00:00.0'
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (HIVE-11640) Shell command doesn't work for new CLI[Beeline-cli branch]

2015-09-07 Thread Hive QA (JIRA) 

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

Hive QA commented on HIVE-11640:




{color:red}Overall{color}: -1 no tests executed

Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12754551/HIVE-11640.8-beeline-cli.patch

Test results: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-BEELINE-Build/33/testReport
Console output: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-BEELINE-Build/33/console
Test logs: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/logs/PreCommit-HIVE-BEELINE-Build-33/

Messages:
{noformat}
Executing org.apache.hive.ptest.execution.PrepPhase
Tests exited with: NonZeroExitCodeException
Command 'bash /data/hive-ptest/working/scratch/source-prep.sh' failed with exit 
status 1 and output '+ [[ -n /usr/java/jdk1.7.0_45-cloudera ]]
+ export JAVA_HOME=/usr/java/jdk1.7.0_45-cloudera
+ JAVA_HOME=/usr/java/jdk1.7.0_45-cloudera
+ export 
PATH=/usr/java/jdk1.7.0_45-cloudera/bin/:/usr/local/apache-maven-3.0.5/bin:/usr/java/jdk1.7.0_45-cloudera/bin:/usr/local/apache-ant-1.9.1/bin:/usr/local/bin:/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/sbin:/home/hiveptest/bin
+ 
PATH=/usr/java/jdk1.7.0_45-cloudera/bin/:/usr/local/apache-maven-3.0.5/bin:/usr/java/jdk1.7.0_45-cloudera/bin:/usr/local/apache-ant-1.9.1/bin:/usr/local/bin:/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/sbin:/home/hiveptest/bin
+ export 'ANT_OPTS=-Xmx1g -XX:MaxPermSize=256m '
+ ANT_OPTS='-Xmx1g -XX:MaxPermSize=256m '
+ export 'M2_OPTS=-Xmx1g -XX:MaxPermSize=256m -Dhttp.proxyHost=localhost 
-Dhttp.proxyPort=3128'
+ M2_OPTS='-Xmx1g -XX:MaxPermSize=256m -Dhttp.proxyHost=localhost 
-Dhttp.proxyPort=3128'
+ cd /data/hive-ptest/working/
+ tee /data/hive-ptest/logs/PreCommit-HIVE-BEELINE-Build-33/source-prep.txt
+ [[ false == \t\r\u\e ]]
+ mkdir -p maven ivy
+ [[ git = \s\v\n ]]
+ [[ git = \g\i\t ]]
+ [[ -z beeline-cli ]]
+ [[ -d apache-git-beeline-source ]]
+ [[ ! -d apache-git-beeline-source/.git ]]
+ [[ ! -d apache-git-beeline-source ]]
+ cd apache-git-beeline-source
+ git fetch origin
>From https://github.com/apache/hive
   3d088de..b90a2ae  beeline-cli -> origin/beeline-cli
   edbbb8b..10dde00  branch-1   -> origin/branch-1
   8026f39..d7fef48  branch-1.0 -> origin/branch-1.0
   dc121c7..4aa432f  branch-1.2 -> origin/branch-1.2
   8b0eded..76828e0  hbase-metastore -> origin/hbase-metastore
   2faf01e..772c4b9  llap   -> origin/llap
   dbdd611..7aec272  master -> origin/master
+ git reset --hard HEAD
HEAD is now at 3d088de HIVE-11637: Support hive.cli.print.current.db in new 
CLI[beeline-cli branch](Ferdinand Xu, reviewed by Dong Chen)
+ git clean -f -d
+ git checkout beeline-cli
Already on 'beeline-cli'
Your branch is behind 'origin/beeline-cli' by 1 commit, and can be 
fast-forwarded.
+ git reset --hard origin/beeline-cli
HEAD is now at b90a2ae HIVE-11640: Shell command doesn't work for new 
CLI[Beeline-cli branch](Ferdinand Xu, reviewed by Xuefu Zhang)
+ git merge --ff-only origin/beeline-cli
Already up-to-date.
+ git gc
+ patchCommandPath=/data/hive-ptest/working/scratch/smart-apply-patch.sh
+ patchFilePath=/data/hive-ptest/working/scratch/build.patch
+ [[ -f /data/hive-ptest/working/scratch/build.patch ]]
+ chmod +x /data/hive-ptest/working/scratch/smart-apply-patch.sh
+ /data/hive-ptest/working/scratch/smart-apply-patch.sh 
/data/hive-ptest/working/scratch/build.patch
The patch does not appear to apply with p0, p1, or p2
+ exit 1
'
{noformat}

This message is automatically generated.

ATTACHMENT ID: 12754551 - PreCommit-HIVE-BEELINE-Build

> Shell command doesn't work for new CLI[Beeline-cli branch]
> --
>
> Key: HIVE-11640
> URL: https://issues.apache.org/jira/browse/HIVE-11640
> Project: Hive
>  Issue Type: Sub-task
>  Components: CLI
>Reporter: Ferdinand Xu
>Assignee: Ferdinand Xu
> Fix For: beeline-cli-branch
>
> Attachments: HIVE-11640.1-beeline-cli.patch, 
> HIVE-11640.2-beeline-cli.patch, HIVE-11640.3-beeline-cli.patch, 
> HIVE-11640.4-beeline-cli.patch, HIVE-11640.5-beeline-cli.patch, 
> HIVE-11640.7-beeline-cli.patch, HIVE-11640.8-beeline-cli.patch
>
>
> The shell command doesn't work for the new CLI and "Error: Method not 
> supported (state=,code=0)" was thrown during the execution for option f and e.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (HIVE-11746) Connect command should not to be allowed from user[beeline-cli branch]

2015-09-07 Thread Xuefu Zhang (JIRA) 

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

Xuefu Zhang commented on HIVE-11746:


Hi [~Ferd], thanks for working on this. I'm not sure if I understand  the 
reason behind of introducing a variable isFromConsole. To me, it seems that 
!connect should be disabled for new Hive CLI regardless whether the command is 
from console or a script file. In addition, Thus, the variable should be really 
"isBeeline", which is already available. Any thoughts?

> Connect command should not to be allowed from user[beeline-cli branch]
> --
>
> Key: HIVE-11746
> URL: https://issues.apache.org/jira/browse/HIVE-11746
> Project: Hive
>  Issue Type: Sub-task
>  Components: Beeline
>Reporter: Ferdinand Xu
>Assignee: Ferdinand Xu
> Attachments: HIVE-11746.1-beeline-cli.patch
>
>
> For new cli, user should not be allowed to connect a server or database.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (HIVE-11647) Bump hbase version to 1.1.1

2015-09-07 Thread Hive QA (JIRA) 

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

Hive QA commented on HIVE-11647:




{color:red}Overall{color}: -1 at least one tests failed

Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12754548/HIVE-11647.2.patch.txt

{color:red}ERROR:{color} -1 due to 2 failed/errored test(s), 9421 tests executed
*Failed tests:*
{noformat}
org.apache.hive.hcatalog.api.TestHCatClient.testTableSchemaPropagation
org.apache.hive.hcatalog.streaming.TestStreaming.testRemainingTransactions
{noformat}

Test results: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/5192/testReport
Console output: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/5192/console
Test logs: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/logs/PreCommit-HIVE-TRUNK-Build-5192/

Messages:
{noformat}
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
Tests exited with: TestsFailedException: 2 tests failed
{noformat}

This message is automatically generated.

ATTACHMENT ID: 12754548 - PreCommit-HIVE-TRUNK-Build

> Bump hbase version to 1.1.1
> ---
>
> Key: HIVE-11647
> URL: https://issues.apache.org/jira/browse/HIVE-11647
> Project: Hive
>  Issue Type: Sub-task
>  Components: HBase Handler
>Reporter: Swarnim Kulkarni
>Assignee: Swarnim Kulkarni
> Attachments: HIVE-11647.1.patch.txt, HIVE-11647.2.patch.txt
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (HIVE-11647) Bump hbase version to 1.1.1

2015-09-07 Thread Swarnim Kulkarni (JIRA) 

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

Swarnim Kulkarni updated HIVE-11647:

Attachment: HIVE-11647.2.patch.txt

Attaching updated patch for testing.

> Bump hbase version to 1.1.1
> ---
>
> Key: HIVE-11647
> URL: https://issues.apache.org/jira/browse/HIVE-11647
> Project: Hive
>  Issue Type: Sub-task
>  Components: HBase Handler
>Reporter: Swarnim Kulkarni
>Assignee: Swarnim Kulkarni
> Attachments: HIVE-11647.1.patch.txt, HIVE-11647.2.patch.txt
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (HIVE-10990) Compatibility Hive-1.2 an hbase-1.0.1.1

2015-09-07 Thread Swarnim Kulkarni (JIRA) 

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

Swarnim Kulkarni resolved HIVE-10990.
-
Resolution: Fixed

> Compatibility Hive-1.2 an hbase-1.0.1.1
> ---
>
> Key: HIVE-10990
> URL: https://issues.apache.org/jira/browse/HIVE-10990
> Project: Hive
>  Issue Type: Bug
>  Components: Beeline, HBase Handler, HiveServer2
>Affects Versions: 1.2.0
>Reporter: gurmukh singh
>Assignee: Swarnim Kulkarni
>
> Hive external table works fine with Hbase.
> Hive-1.2 and hbase-1.0.1.1, hadoop-2.5.2
> Not able to create a table from hive in hbase.
> 1: jdbc:hive2://edge1.dilithium.com:1/def> TBLPROPERTIES 
> ("hbase.table.name" = "xyz");
> FAILED: Execution Error, return code 1 from 
> org.apache.hadoop.hive.ql.exec.DDLTask. 
> org.apache.hadoop.hbase.HTableDescriptor.addFamily(Lorg/apache/hadoop/hbase/HColumnDescriptor;)V
> Error: Error while processing statement: FAILED: Execution Error, return code 
> 1 from org.apache.hadoop.hive.ql.exec.DDLTask. 
> org.apache.hadoop.hbase.HTableDescriptor.addFamily(Lorg/apache/hadoop/hbase/HColumnDescriptor;)V
>  (state=08S01,code=1)
> [hdfs@edge1 cluster]$ hive
> 2015-06-12 17:56:49,952 WARN  [main] conf.HiveConf: HiveConf of name 
> hive.metastore.local does not exist
> Logging initialized using configuration in 
> jar:file:/usr/local/cluster/apache-hive-1.2.0-bin/lib/hive-common-1.2.0.jar!/hive-log4j.properties
> SLF4J: Class path contains multiple SLF4J bindings.
> SLF4J: Found binding in 
> [jar:file:/usr/local/cluster/apache-hive-1.2.0-bin/auxlib/slf4j-log4j12-1.7.7.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: Found binding in 
> [jar:file:/usr/local/cluster/hadoop-2.5.2/share/hadoop/common/lib/slf4j-log4j12-1.7.5.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an 
> explanation.
> SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory]
> hive> CREATE TABLE hbase_table_1(key int, value string)
> > STORED BY 'org.apache.hadoop.hive.hbase.HBaseStorageHandler'
> > WITH SERDEPROPERTIES ("hbase.columns.mapping" = ":key,cf1:val")
> > TBLPROPERTIES ("hbase.table.name" = "xyz");
> FAILED: Execution Error, return code 1 from 
> org.apache.hadoop.hive.ql.exec.DDLTask. 
> org.apache.hadoop.hbase.HTableDescriptor.addFamily(Lorg/apache/hadoop/hbase/HColumnDescriptor;)V
> ===
> scan complete in 1535ms
> 14 driver classes found
> Compliant Version Driver Class
> no5.1 com.mysql.jdbc.Driver
> no5.1 com.mysql.jdbc.NonRegisteringDriver
> no5.1 com.mysql.jdbc.NonRegisteringReplicationDriver
> no5.1 com.mysql.jdbc.ReplicationDriver
> yes   1.2 org.apache.calcite.avatica.remote.Driver
> yes   1.2 org.apache.calcite.jdbc.Driver
> yes   1.0 org.apache.commons.dbcp.PoolingDriver
> yes   10.11   org.apache.derby.jdbc.AutoloadedDriver
> yes   10.11   org.apache.derby.jdbc.Driver42
> yes   10.11   org.apache.derby.jdbc.EmbeddedDriver
> yes   10.11   org.apache.derby.jdbc.InternalDriver
> no1.2 org.apache.hive.jdbc.HiveDriver
> yes   1.0 org.datanucleus.store.rdbms.datasource.dbcp.PoolingDriver
> no5.1 org.gjt.mm.mysql.Driver



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (HIVE-11706) Implement "show create database"

2015-09-07 Thread Navis (JIRA) 

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

Navis updated HIVE-11706:
-
Attachment: HIVE-11706.2.patch.txt

Fixed test fails

> Implement "show create database"
> 
>
> Key: HIVE-11706
> URL: https://issues.apache.org/jira/browse/HIVE-11706
> Project: Hive
>  Issue Type: New Feature
>  Components: Metastore
>Reporter: Navis
>Assignee: Navis
>Priority: Trivial
> Attachments: HIVE-11706.1.patch.txt, HIVE-11706.2.patch.txt
>
>
> HIVE-967 introduced "show create table". How about "show create database"?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (HIVE-11662) Dynamic partitioning cannot be applied to external table which contains part-spec like directory name

2015-09-07 Thread Navis (JIRA) 

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

Navis updated HIVE-11662:
-
Summary: Dynamic partitioning cannot be applied to external table which 
contains part-spec like directory name  (was: DP cannot be applied to external 
table which contains part-spec like directory)

> Dynamic partitioning cannot be applied to external table which contains 
> part-spec like directory name
> -
>
> Key: HIVE-11662
> URL: https://issues.apache.org/jira/browse/HIVE-11662
> Project: Hive
>  Issue Type: Bug
>  Components: Query Processor
>Reporter: Navis
>Assignee: Navis
>Priority: Trivial
> Attachments: HIVE-11662.1.patch.txt, HIVE-11662.2.patch.txt
>
>
> Some users want to use part-spec like directory name in their partitioned 
> table locations, something like,
> {noformat}
> /something/warehouse/some_key=some_value
> {noformat}
> DP calculates additional partitions from full path, and makes exception 
> something like,
> {noformat}
> Failed with exception Partition spec {some_key=some_value, 
> part_key=part_value} contains non-partition columns
> FAILED: Execution Error, return code 1 from 
> org.apache.hadoop.hive.ql.exec.MoveTask
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (HIVE-11662) DP cannot be applied to external table which contains part-spec like directory

2015-09-07 Thread Navis (JIRA) 

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

Navis commented on HIVE-11662:
--

[~leftylev] Right. I'll rename the issue description.

> DP cannot be applied to external table which contains part-spec like directory
> --
>
> Key: HIVE-11662
> URL: https://issues.apache.org/jira/browse/HIVE-11662
> Project: Hive
>  Issue Type: Bug
>  Components: Query Processor
>Reporter: Navis
>Assignee: Navis
>Priority: Trivial
> Attachments: HIVE-11662.1.patch.txt, HIVE-11662.2.patch.txt
>
>
> Some users want to use part-spec like directory name in their partitioned 
> table locations, something like,
> {noformat}
> /something/warehouse/some_key=some_value
> {noformat}
> DP calculates additional partitions from full path, and makes exception 
> something like,
> {noformat}
> Failed with exception Partition spec {some_key=some_value, 
> part_key=part_value} contains non-partition columns
> FAILED: Execution Error, return code 1 from 
> org.apache.hadoop.hive.ql.exec.MoveTask
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (HIVE-11752) Pre-materializing complex CTE queries

2015-09-07 Thread Navis (JIRA) 

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

Navis updated HIVE-11752:
-
Attachment: HIVE-11752.1.patch.txt

Patch for preliminary test.

> Pre-materializing complex CTE queries
> -
>
> Key: HIVE-11752
> URL: https://issues.apache.org/jira/browse/HIVE-11752
> Project: Hive
>  Issue Type: Improvement
>  Components: Query Processor
>Reporter: Navis
>Assignee: Navis
>Priority: Minor
> Attachments: HIVE-11752.1.patch.txt
>
>
> Currently, hive regards CTE clauses as a simple alias to the query block, 
> which makes redundant works if it's used multiple times in a query. This 
> introduces a reference threshold for pre-materializing the CTE clause as a 
> volatile table (which is not exists in any form of metastore and just 
> accessible from QB).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (HIVE-11640) Shell command doesn't work for new CLI[Beeline-cli branch]

2015-09-07 Thread Ferdinand Xu (JIRA) 

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

Ferdinand Xu updated HIVE-11640:

Attachment: HIVE-11640.8-beeline-cli.patch

> Shell command doesn't work for new CLI[Beeline-cli branch]
> --
>
> Key: HIVE-11640
> URL: https://issues.apache.org/jira/browse/HIVE-11640
> Project: Hive
>  Issue Type: Sub-task
>  Components: CLI
>Reporter: Ferdinand Xu
>Assignee: Ferdinand Xu
> Attachments: HIVE-11640.1-beeline-cli.patch, 
> HIVE-11640.2-beeline-cli.patch, HIVE-11640.3-beeline-cli.patch, 
> HIVE-11640.4-beeline-cli.patch, HIVE-11640.5-beeline-cli.patch, 
> HIVE-11640.7-beeline-cli.patch, HIVE-11640.8-beeline-cli.patch
>
>
> The shell command doesn't work for the new CLI and "Error: Method not 
> supported (state=,code=0)" was thrown during the execution for option f and e.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (HIVE-11754) Not reachable code parts in StatsUtils

2015-09-07 Thread Navis (JIRA) 

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

Navis updated HIVE-11754:
-
Attachment: HIVE-11754.1.patch.txt

> Not reachable code parts in StatsUtils
> --
>
> Key: HIVE-11754
> URL: https://issues.apache.org/jira/browse/HIVE-11754
> Project: Hive
>  Issue Type: Task
>Reporter: Navis
>Assignee: Navis
>Priority: Trivial
> Attachments: HIVE-11754.1.patch.txt
>
>
> No need to check "oi instanceof WritableConstantHiveCharObjectInspector" 
> after "oi instanceof ConstantObjectInspector".



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (HIVE-10890) Provide implementable engine selector

2015-09-07 Thread Hive QA (JIRA) 

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

Hive QA commented on HIVE-10890:




{color:red}Overall{color}: -1 no tests executed

Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12754556/HIVE-10890.2.patch.txt

Test results: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/5194/testReport
Console output: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/5194/console
Test logs: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/logs/PreCommit-HIVE-TRUNK-Build-5194/

Messages:
{noformat}
Executing org.apache.hive.ptest.execution.PrepPhase
Tests exited with: NonZeroExitCodeException
Command 'bash /data/hive-ptest/working/scratch/source-prep.sh' failed with exit 
status 1 and output '+ [[ -n /usr/java/jdk1.7.0_45-cloudera ]]
+ export JAVA_HOME=/usr/java/jdk1.7.0_45-cloudera
+ JAVA_HOME=/usr/java/jdk1.7.0_45-cloudera
+ export 
PATH=/usr/java/jdk1.7.0_45-cloudera/bin/:/usr/local/apache-maven-3.0.5/bin:/usr/java/jdk1.7.0_45-cloudera/bin:/usr/local/apache-ant-1.9.1/bin:/usr/local/bin:/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/sbin:/home/hiveptest/bin
+ 
PATH=/usr/java/jdk1.7.0_45-cloudera/bin/:/usr/local/apache-maven-3.0.5/bin:/usr/java/jdk1.7.0_45-cloudera/bin:/usr/local/apache-ant-1.9.1/bin:/usr/local/bin:/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/sbin:/home/hiveptest/bin
+ export 'ANT_OPTS=-Xmx1g -XX:MaxPermSize=256m '
+ ANT_OPTS='-Xmx1g -XX:MaxPermSize=256m '
+ export 'M2_OPTS=-Xmx1g -XX:MaxPermSize=256m -Dhttp.proxyHost=localhost 
-Dhttp.proxyPort=3128'
+ M2_OPTS='-Xmx1g -XX:MaxPermSize=256m -Dhttp.proxyHost=localhost 
-Dhttp.proxyPort=3128'
+ cd /data/hive-ptest/working/
+ tee /data/hive-ptest/logs/PreCommit-HIVE-TRUNK-Build-5194/source-prep.txt
+ [[ false == \t\r\u\e ]]
+ mkdir -p maven ivy
+ [[ git = \s\v\n ]]
+ [[ git = \g\i\t ]]
+ [[ -z master ]]
+ [[ -d apache-github-source-source ]]
+ [[ ! -d apache-github-source-source/.git ]]
+ [[ ! -d apache-github-source-source ]]
+ cd apache-github-source-source
+ git fetch origin
+ git reset --hard HEAD
HEAD is now at 7aec272 HIVE-11737: IndexOutOfBounds compiling query with 
duplicated groupby keys (Jimmy, reviewed by Szehon)
+ git clean -f -d
+ git checkout master
Already on 'master'
+ git reset --hard origin/master
HEAD is now at 7aec272 HIVE-11737: IndexOutOfBounds compiling query with 
duplicated groupby keys (Jimmy, reviewed by Szehon)
+ git merge --ff-only origin/master
Already up-to-date.
+ git gc
+ patchCommandPath=/data/hive-ptest/working/scratch/smart-apply-patch.sh
+ patchFilePath=/data/hive-ptest/working/scratch/build.patch
+ [[ -f /data/hive-ptest/working/scratch/build.patch ]]
+ chmod +x /data/hive-ptest/working/scratch/smart-apply-patch.sh
+ /data/hive-ptest/working/scratch/smart-apply-patch.sh 
/data/hive-ptest/working/scratch/build.patch
The patch does not appear to apply with p0, p1, or p2
+ exit 1
'
{noformat}

This message is automatically generated.

ATTACHMENT ID: 12754556 - PreCommit-HIVE-TRUNK-Build

> Provide implementable engine selector
> -
>
> Key: HIVE-10890
> URL: https://issues.apache.org/jira/browse/HIVE-10890
> Project: Hive
>  Issue Type: Improvement
>  Components: Query Processor
>Reporter: Navis
>Assignee: Navis
>Priority: Trivial
> Attachments: HIVE-10890.1.patch.txt, HIVE-10890.2.patch.txt
>
>
> Now hive supports three kind of engines. It would be good to have an 
> automatic engine selector without setting explicitly engine for execution.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (HIVE-11751) hive-exec-log4j2.xml settings causes DEBUG messages to be generated and ignored

2015-09-07 Thread Rajesh Balamohan (JIRA) 

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

Rajesh Balamohan updated HIVE-11751:

Attachment: hiveserver2_log4j.png

> hive-exec-log4j2.xml settings causes DEBUG messages to be generated and 
> ignored
> ---
>
> Key: HIVE-11751
> URL: https://issues.apache.org/jira/browse/HIVE-11751
> Project: Hive
>  Issue Type: Bug
>Reporter: Rajesh Balamohan
> Attachments: hiveserver2_log4j.png
>
>
> Setting "INFO" in 
> dist/hive/conf/hive-exec-log4j2.xml fixes the problem. Should it be made as 
> default in hive-exec-log4j2.xml? "--hiveconf hive.log.level=INFO" from 
> commandline does not have any impact.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (HIVE-10890) Provide implementable engine selector

2015-09-07 Thread Navis (JIRA) 

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

Navis updated HIVE-10890:
-
Attachment: HIVE-10890.2.patch.txt

rebased to trunk

> Provide implementable engine selector
> -
>
> Key: HIVE-10890
> URL: https://issues.apache.org/jira/browse/HIVE-10890
> Project: Hive
>  Issue Type: Improvement
>  Components: Query Processor
>Reporter: Navis
>Assignee: Navis
>Priority: Trivial
> Attachments: HIVE-10890.1.patch.txt, HIVE-10890.2.patch.txt
>
>
> Now hive supports three kind of engines. It would be good to have an 
> automatic engine selector without setting explicitly engine for execution.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (HIVE-11640) Shell command doesn't work for new CLI[Beeline-cli branch]

2015-09-07 Thread Xuefu Zhang (JIRA) 

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

Xuefu Zhang commented on HIVE-11640:


+1

> Shell command doesn't work for new CLI[Beeline-cli branch]
> --
>
> Key: HIVE-11640
> URL: https://issues.apache.org/jira/browse/HIVE-11640
> Project: Hive
>  Issue Type: Sub-task
>  Components: CLI
>Reporter: Ferdinand Xu
>Assignee: Ferdinand Xu
> Attachments: HIVE-11640.1-beeline-cli.patch, 
> HIVE-11640.2-beeline-cli.patch, HIVE-11640.3-beeline-cli.patch, 
> HIVE-11640.4-beeline-cli.patch, HIVE-11640.5-beeline-cli.patch, 
> HIVE-11640.7-beeline-cli.patch, HIVE-11640.8-beeline-cli.patch
>
>
> The shell command doesn't work for the new CLI and "Error: Method not 
> supported (state=,code=0)" was thrown during the execution for option f and e.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (HIVE-11755) Incorrect method called with Kerberos enabled in AccumuloStorageHandler

2015-09-07 Thread Josh Elser (JIRA) 

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

Josh Elser updated HIVE-11755:
--
Attachment: HIVE-11755.001.patch

Initial patch. Unit tests passed (will let Hive-QA run for the itests).

Obvious error in the code (calling the parent method instead of the local 
method -- thanks static methods). Tested via some excessive mocking.

> Incorrect method called with Kerberos enabled in AccumuloStorageHandler
> ---
>
> Key: HIVE-11755
> URL: https://issues.apache.org/jira/browse/HIVE-11755
> Project: Hive
>  Issue Type: Bug
>Affects Versions: 1.2.1
>Reporter: Josh Elser
>Assignee: Josh Elser
> Fix For: 1.2.2
>
> Attachments: HIVE-11755.001.patch
>
>
> The following exception was noticed in testing out the 
> AccumuloStorageHandler's OutputFormat:
> {noformat}
> java.lang.IllegalStateException: Connector info for AccumuloOutputFormat can 
> only be set once per job
>   at 
> org.apache.accumulo.core.client.mapreduce.lib.impl.ConfiguratorBase.setConnectorInfo(ConfiguratorBase.java:146)
>   at 
> org.apache.accumulo.core.client.mapred.AccumuloOutputFormat.setConnectorInfo(AccumuloOutputFormat.java:125)
>   at 
> org.apache.hadoop.hive.accumulo.mr.HiveAccumuloTableOutputFormat.configureAccumuloOutputFormat(HiveAccumuloTableOutputFormat.java:95)
>   at 
> org.apache.hadoop.hive.accumulo.mr.HiveAccumuloTableOutputFormat.checkOutputSpecs(HiveAccumuloTableOutputFormat.java:51)
>   at 
> org.apache.hadoop.hive.ql.io.HivePassThroughOutputFormat.checkOutputSpecs(HivePassThroughOutputFormat.java:46)
>   at 
> org.apache.hadoop.hive.ql.exec.FileSinkOperator.checkOutputSpecs(FileSinkOperator.java:1124)
>   at 
> org.apache.hadoop.hive.ql.io.HiveOutputFormatImpl.checkOutputSpecs(HiveOutputFormatImpl.java:67)
>   at 
> org.apache.hadoop.mapreduce.JobSubmitter.checkSpecs(JobSubmitter.java:268)
>   at 
> org.apache.hadoop.mapreduce.JobSubmitter.submitJobInternal(JobSubmitter.java:139)
>   at org.apache.hadoop.mapreduce.Job$10.run(Job.java:1290)
>   at org.apache.hadoop.mapreduce.Job$10.run(Job.java:1287)
>   at java.security.AccessController.doPrivileged(Native Method)
>   at javax.security.auth.Subject.doAs(Subject.java:415)
>   at 
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1657)
>   at org.apache.hadoop.mapreduce.Job.submit(Job.java:1287)
>   at org.apache.hadoop.mapred.JobClient$1.run(JobClient.java:575)
>   at org.apache.hadoop.mapred.JobClient$1.run(JobClient.java:570)
>   at java.security.AccessController.doPrivileged(Native Method)
>   at javax.security.auth.Subject.doAs(Subject.java:415)
>   at 
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1657)
>   at org.apache.hadoop.mapred.JobClient.submitJobInternal(JobClient.java:570)
>   at org.apache.hadoop.mapred.JobClient.submitJob(JobClient.java:561)
>   at org.apache.hadoop.hive.ql.exec.mr.ExecDriver.execute(ExecDriver.java:431)
>   at org.apache.hadoop.hive.ql.exec.mr.MapRedTask.execute(MapRedTask.java:137)
>   at org.apache.hadoop.hive.ql.exec.Task.executeTask(Task.java:160)
>   at 
> org.apache.hadoop.hive.ql.exec.TaskRunner.runSequential(TaskRunner.java:88)
>   at org.apache.hadoop.hive.ql.Driver.launchTask(Driver.java:1653)
>   at org.apache.hadoop.hive.ql.Driver.execute(Driver.java:1412)
>   at org.apache.hadoop.hive.ql.Driver.runInternal(Driver.java:1195)
>   at org.apache.hadoop.hive.ql.Driver.run(Driver.java:1059)
>   at org.apache.hadoop.hive.ql.Driver.run(Driver.java:1049)
>   at org.apache.hadoop.hive.cli.CliDriver.processLocalCmd(CliDriver.java:213)
>   at org.apache.hadoop.hive.cli.CliDriver.processCmd(CliDriver.java:165)
>   at org.apache.hadoop.hive.cli.CliDriver.processLine(CliDriver.java:376)
>   at org.apache.hadoop.hive.cli.CliDriver.processLine(CliDriver.java:311)
>   at org.apache.hadoop.hive.cli.CliDriver.processReader(CliDriver.java:409)
>   at org.apache.hadoop.hive.cli.CliDriver.processFile(CliDriver.java:425)
>   at org.apache.hadoop.hive.cli.CliDriver.executeDriver(CliDriver.java:714)
>   at org.apache.hadoop.hive.cli.CliDriver.run(CliDriver.java:681)
>   at org.apache.hadoop.hive.cli.CliDriver.main(CliDriver.java:621)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:606)
>   at org.apache.hadoop.util.RunJar.run(RunJar.java:221)
>   at org.apache.hadoop.util.RunJar.main(RunJar.java:136)
>   Job Submission failed with exception 
> 'java.lang.IllegalStateException(Connector info for AccumuloOutputFormat can 
> only be set once per job)'
> {noformat}
>

[jira] [Updated] (HIVE-11640) Shell command doesn't work for new CLI[Beeline-cli branch]

2015-09-07 Thread Ferdinand Xu (JIRA) 

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

Ferdinand Xu updated HIVE-11640:

Fix Version/s: beeline-cli-branch

> Shell command doesn't work for new CLI[Beeline-cli branch]
> --
>
> Key: HIVE-11640
> URL: https://issues.apache.org/jira/browse/HIVE-11640
> Project: Hive
>  Issue Type: Sub-task
>  Components: CLI
>Reporter: Ferdinand Xu
>Assignee: Ferdinand Xu
> Fix For: beeline-cli-branch
>
> Attachments: HIVE-11640.1-beeline-cli.patch, 
> HIVE-11640.2-beeline-cli.patch, HIVE-11640.3-beeline-cli.patch, 
> HIVE-11640.4-beeline-cli.patch, HIVE-11640.5-beeline-cli.patch, 
> HIVE-11640.7-beeline-cli.patch, HIVE-11640.8-beeline-cli.patch
>
>
> The shell command doesn't work for the new CLI and "Error: Method not 
> supported (state=,code=0)" was thrown during the execution for option f and e.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (HIVE-11746) Connect command should not to be allowed from user[beeline-cli branch]

2015-09-07 Thread Ferdinand Xu (JIRA) 

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

Ferdinand Xu commented on HIVE-11746:
-

Hi [~xuefuz], can you help review this jira? Thank you!

> Connect command should not to be allowed from user[beeline-cli branch]
> --
>
> Key: HIVE-11746
> URL: https://issues.apache.org/jira/browse/HIVE-11746
> Project: Hive
>  Issue Type: Sub-task
>  Components: Beeline
>Reporter: Ferdinand Xu
>Assignee: Ferdinand Xu
> Attachments: HIVE-11746.1-beeline-cli.patch
>
>
> For new cli, user should not be allowed to connect a server or database.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (HIVE-11703) Make RegExp and RLike reserved keywords

2015-09-07 Thread Pengcheng Xiong (JIRA) 

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

Pengcheng Xiong commented on HIVE-11703:


[~leftylev], thanks for your comments. I have modified the wiki accordingly.

> Make RegExp and RLike reserved keywords
> ---
>
> Key: HIVE-11703
> URL: https://issues.apache.org/jira/browse/HIVE-11703
> Project: Hive
>  Issue Type: Sub-task
>Reporter: Pengcheng Xiong
>Assignee: Pengcheng Xiong
> Fix For: 2.0.0
>
>
> RegExp and RLike are treated as "precedenceEqualNegatableOperator" in Hive. 
> They actually come from MySQL. Both of them are not keywords in SQL2011. But 
> they are reserved keywords in MySQL. Making them reserved ones can eliminate 
> the current 14 ambiguities that we have in current Hive. If users still would 
> like to use them as identifiers/function names, users can "set 
> hive.support.sql11.reserved.keywords=false;"



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)