[jira] [Commented] (HIVE-6595) Hive 0.11.0 build failure

2017-05-23 Thread Shawn Lavelle (JIRA) 

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

Shawn Lavelle commented on HIVE-6595:
-

For completeness, could this be accomplished by compiling with the 1.6 JDK?

> Hive 0.11.0 build failure
> -
>
> Key: HIVE-6595
> URL: https://issues.apache.org/jira/browse/HIVE-6595
> Project: Hive
>  Issue Type: Bug
>  Components: Build Infrastructure
>Affects Versions: 0.11.0
> Environment: CentOS 6.5, java version "1.7.0_45", Hadoop 2.2.0
>Reporter: Amit Anand
>Assignee: Szehon Ho
>
> I am unable to build Hive 0.11.0 from the source. I have a single node hadoop 
> 2.2.0, that I built from the source, running. 
> I followed steps given below:
> svn co http://svn.apache.org/repos/asf/hive/tags/release-0.11.0/ hive-0.11.0
> cd hive-0.11.0
> ant clean
> ant package
> I got messages given below 
> compile:
>  [echo] Project: jdbc
> [javac] Compiling 28 source files to 
> /opt/apache/source/hive-0.11.0/build/jdbc/classes
> [javac] 
> /opt/apache/source/hive-0.11.0/jdbc/src/java/org/apache/hive/jdbc/HiveCallableStatement.java:48:
>  error: HiveCallableStatement is not abstract and does not override abstract 
> method getObject(String,Class) in CallableStatement
> [javac] public class HiveCallableStatement implements 
> java.sql.CallableStatement {
> [javac]^
> [javac]   where T is a type-variable:
> [javac] T extends Object declared in method 
> getObject(String,Class)
> [javac] 
> /opt/apache/source/hive-0.11.0/jdbc/src/java/org/apache/hive/jdbc/HiveConnection.java:65:
>  error: HiveConnection is not abstract and does not override abstract method 
> getNetworkTimeout() in Connection
> [javac] public class HiveConnection implements java.sql.Connection {
> [javac]^
> [javac] 
> /opt/apache/source/hive-0.11.0/jdbc/src/java/org/apache/hive/jdbc/HiveDataSource.java:31:
>  error: HiveDataSource is not abstract and does not override abstract method 
> getParentLogger() in CommonDataSource
> [javac] public class HiveDataSource implements DataSource {
> [javac]^
> [javac] 
> /opt/apache/source/hive-0.11.0/jdbc/src/java/org/apache/hive/jdbc/HiveDatabaseMetaData.java:56:
>  error: HiveDatabaseMetaData is not abstract and does not override abstract 
> method generatedKeyAlwaysReturned() in DatabaseMetaData
> [javac] public class HiveDatabaseMetaData implements DatabaseMetaData {
> [javac]^
> [javac] 
> /opt/apache/source/hive-0.11.0/jdbc/src/java/org/apache/hive/jdbc/HiveDatabaseMetaData.java:707:
>  error:  is not 
> abstract and does not override abstract method getObject(String,Class) 
> in ResultSet
> [javac] , null) {
> [javac] ^
> [javac]   where T is a type-variable:
> [javac] T extends Object declared in method 
> getObject(String,Class)
> [javac] 
> /opt/apache/source/hive-0.11.0/jdbc/src/java/org/apache/hive/jdbc/HiveDriver.java:35:
>  error: HiveDriver is not abstract and does not override abstract method 
> getParentLogger() in Driver
> [javac] public class HiveDriver implements Driver {
> [javac]^
> [javac] 
> /opt/apache/source/hive-0.11.0/jdbc/src/java/org/apache/hive/jdbc/HivePreparedStatement.java:56:
>  error: HivePreparedStatement is not abstract and does not override abstract 
> method isCloseOnCompletion() in Statement
> [javac] public class HivePreparedStatement implements PreparedStatement {
> [javac]^
> [javac] 
> /opt/apache/source/hive-0.11.0/jdbc/src/java/org/apache/hive/jdbc/HiveQueryResultSet.java:48:
>  error: HiveQueryResultSet is not abstract and does not override abstract 
> method getObject(String,Class) in ResultSet
> [javac] public class HiveQueryResultSet extends HiveBaseResultSet {
> [javac]^
> [javac]   where T is a type-variable:
> [javac] T extends Object declared in method 
> getObject(String,Class)
> [javac] 
> /opt/apache/source/hive-0.11.0/jdbc/src/java/org/apache/hive/jdbc/HiveStatement.java:42:
>  error: HiveStatement is not abstract and does not override abstract method 
> isCloseOnCompletion() in Statement
> [javac] public class HiveStatement implements java.sql.Statement {
> [javac]^
> [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.
> [javac] 9 errors
> BUILD FAILED
> /opt/apache/source/hive-0.11.0/build.xml:274: The following error occurred 
> while executing this line:
> /opt/apache/source/hive-0.11.0/build.xml:113: The following error occurred 
>

[jira] [Commented] (HIVE-11555) Beeline sends password in clear text if we miss -ssl=true flag in the connect string

2017-05-19 Thread Shawn Lavelle (JIRA) 

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

Shawn Lavelle commented on HIVE-11555:
--

I think ... plaintext passwords should *never* be sent across the wire

> Beeline sends password in clear text if we miss -ssl=true flag in the connect 
> string
> 
>
> Key: HIVE-11555
> URL: https://issues.apache.org/jira/browse/HIVE-11555
> Project: Hive
>  Issue Type: Bug
>  Components: Beeline
>Affects Versions: 1.2.0
>Reporter: bharath v
>Assignee: Junjie Chen
>
> {code}
> I used tcpdump to display the network traffic: 
> [root@fe01 ~]# beeline 
> Beeline version 0.13.1-cdh5.3.2 by Apache Hive 
> beeline> !connect jdbc:hive2://fe01.sectest.poc:1/default 
> Connecting to jdbc:hive2://fe01.sectest.poc:1/default 
> Enter username for jdbc:hive2://fe01.sectest.poc:1/default: tdaranyi 
> Enter password for jdbc:hive2://fe01.sectest.poc:1/default: * 
> (I entered "cleartext" as the password) 
> The tcpdump in a different window 
> tdara...@fe01.sectest.poc:~$ sudo tcpdump -n -X -i lo port 1 
> tcpdump: verbose output suppressed, use -v or -vv for full protocol decode 
> listening on lo, link-type EN10MB (Ethernet), capture size 65535 bytes 
> (...) 
> 10:25:16.329974 IP 192.168.32.102.54322 > 192.168.32.102.ndmp: Flags [P.], 
> seq 11:35, ack 1, win 512, options [nop,nop,TS val 2412851969 ecr 
> 2412851969], length 24 
> 0x: 4500 004c 3dd3 4000 4006 3abc c0a8 2066 E..L=.@.@.:f 
> 0x0010: c0a8 2066 d432 2710 714c 0edc b45c 9268 ...f.2'.qL...\.h 
> 0x0020: 8018 0200 c25b  0101 080a 8fd1 3301 .[3. 
> 0x0030: 8fd1 3301 0500  1300 7464 6172 616e ..3...tdaran 
> 0x0040: 7969 0063 6c65 6172 7465 7874 yi.cleartext 
> (...) 
> {code}
> We rely on the user supplied configuration to decide whether to open an SSL 
> socket or a Plain one. Instead we can negotiate this information from the HS2 
> and connect accordingly.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Comment Edited] (HIVE-6852) JDBC client connections hang at TSaslTransport

2016-09-08 Thread Shawn Lavelle (JIRA) 

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

Shawn Lavelle edited comment on HIVE-6852 at 9/8/16 3:03 PM:
-

Any thoughts on this being a known JDK issue?
http://bugs.java.com/bugdatabase/view_bug.do?bug_id=8075484
(https://bugs.openjdk.java.net/browse/JDK-8049846)
(https://bugs.openjdk.java.net/browse/JDK-8075484)

Here's my stack trace using CUSTOM authentication on Hive 0.11:

{code:title=Debug Output|borderStyle=solid}
16/09/08 09:36:48 DEBUG TSaslTransport: opening transport 
org.apache.thrift.transpor58
16/09/08 09:36:48 DEBUG TSaslClientTransport: Sending mechanism name PLAIN and 
initi
16/09/08 09:36:48 DEBUG TSaslTransport: CLIENT: Writing message with status 
START an
16/09/08 09:36:48 DEBUG TSaslTransport: CLIENT: Writing message with status 
COMPLETE
16/09/08 09:36:48 DEBUG TSaslTransport: CLIENT: Start message handled
16/09/08 09:36:48 DEBUG TSaslTransport: CLIENT: Main negotiation loop complete
16/09/08 09:36:48 DEBUG TSaslTransport: CLIENT: SASL Client receiving last 
message
{code}

{code:title=Partial Stack Trace|borderStyle=solid}
"main" #1 prio=5 os_prio=0 tid=0x0049f800 nid=0x409c runnable 
[0x0024d000]
   java.lang.Thread.State: RUNNABLE
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.socketRead(SocketInputStream.java:116)
at java.net.SocketInputStream.read(SocketInputStream.java:170)
at java.net.SocketInputStream.read(SocketInputStream.java:141)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:246)
at java.io.BufferedInputStream.read1(BufferedInputStream.java:286)
at java.io.BufferedInputStream.read(BufferedInputStream.java:345)
- locked <0x000716426228> (a java.io.BufferedInputStream)
at 
org.apache.thrift.transport.TIOStreamTransport.read(TIOStreamTransport.java:127)
at org.apache.thrift.transport.TTransport.readAll(TTransport.java:84)
at 
org.apache.thrift.transport.TSaslTransport.receiveSaslMessage(TSaslTransport.java:178)
at 
org.apache.thrift.transport.TSaslTransport.open(TSaslTransport.java:288)
at 
org.apache.thrift.transport.TSaslClientTransport.open(TSaslClientTransport.java:37)
at 
org.apache.hive.jdbc.HiveConnection.openTransport(HiveConnection.java:157)
{code}


was (Author: azeroth2b):
Any thoughts on this being a known JDK issue?
https://bugs.openjdk.java.net/browse/JDK-8049846
https://bugs.openjdk.java.net/browse/JDK-8075484

Here's my stack trace using CUSTOM authentication on Hive 0.11:

{code:title=Debug Output|borderStyle=solid}
16/09/08 09:36:48 DEBUG TSaslTransport: opening transport 
org.apache.thrift.transpor58
16/09/08 09:36:48 DEBUG TSaslClientTransport: Sending mechanism name PLAIN and 
initi
16/09/08 09:36:48 DEBUG TSaslTransport: CLIENT: Writing message with status 
START an
16/09/08 09:36:48 DEBUG TSaslTransport: CLIENT: Writing message with status 
COMPLETE
16/09/08 09:36:48 DEBUG TSaslTransport: CLIENT: Start message handled
16/09/08 09:36:48 DEBUG TSaslTransport: CLIENT: Main negotiation loop complete
16/09/08 09:36:48 DEBUG TSaslTransport: CLIENT: SASL Client receiving last 
message
{code}

{code:title=Partial Stack Trace|borderStyle=solid}
"main" #1 prio=5 os_prio=0 tid=0x0049f800 nid=0x409c runnable 
[0x0024d000]
   java.lang.Thread.State: RUNNABLE
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.socketRead(SocketInputStream.java:116)
at java.net.SocketInputStream.read(SocketInputStream.java:170)
at java.net.SocketInputStream.read(SocketInputStream.java:141)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:246)
at java.io.BufferedInputStream.read1(BufferedInputStream.java:286)
at java.io.BufferedInputStream.read(BufferedInputStream.java:345)
- locked <0x000716426228> (a java.io.BufferedInputStream)
at 
org.apache.thrift.transport.TIOStreamTransport.read(TIOStreamTransport.java:127)
at org.apache.thrift.transport.TTransport.readAll(TTransport.java:84)
at 
org.apache.thrift.transport.TSaslTransport.receiveSaslMessage(TSaslTransport.java:178)
at 
org.apache.thrift.transport.TSaslTransport.open(TSaslTransport.java:288)
at 
org.apache.thrift.transport.TSaslClientTransport.open(TSaslClientTransport.java:37)
at 
org.apache.hive.jdbc.HiveConnection.openTransport(HiveConnection.java:157)
{code}

> JDBC client connections hang at TSaslTransport
> --
>
> Key: HIVE-6852
> URL: https://issues.apache.org/jira/browse/HIVE-6852
> Project: Hive
>  Issue Type: Bug
>  Components: JDBC
>Reporter: jay vyas
>
> I've noticed that

[jira] [Comment Edited] (HIVE-6852) JDBC client connections hang at TSaslTransport

2016-09-08 Thread Shawn Lavelle (JIRA) 

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

Shawn Lavelle edited comment on HIVE-6852 at 9/8/16 2:52 PM:
-

Any thoughts on this being a known JDK issue?
https://bugs.openjdk.java.net/browse/JDK-8049846
https://bugs.openjdk.java.net/browse/JDK-8075484

Here's my stack trace using CUSTOM authentication on Hive 0.11:

{code:title=Debug Output|borderStyle=solid}
16/09/08 09:36:48 DEBUG TSaslTransport: opening transport 
org.apache.thrift.transpor58
16/09/08 09:36:48 DEBUG TSaslClientTransport: Sending mechanism name PLAIN and 
initi
16/09/08 09:36:48 DEBUG TSaslTransport: CLIENT: Writing message with status 
START an
16/09/08 09:36:48 DEBUG TSaslTransport: CLIENT: Writing message with status 
COMPLETE
16/09/08 09:36:48 DEBUG TSaslTransport: CLIENT: Start message handled
16/09/08 09:36:48 DEBUG TSaslTransport: CLIENT: Main negotiation loop complete
16/09/08 09:36:48 DEBUG TSaslTransport: CLIENT: SASL Client receiving last 
message
{code}

{code:title=Partial Stack Trace|borderStyle=solid}
"main" #1 prio=5 os_prio=0 tid=0x0049f800 nid=0x409c runnable 
[0x0024d000]
   java.lang.Thread.State: RUNNABLE
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.socketRead(SocketInputStream.java:116)
at java.net.SocketInputStream.read(SocketInputStream.java:170)
at java.net.SocketInputStream.read(SocketInputStream.java:141)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:246)
at java.io.BufferedInputStream.read1(BufferedInputStream.java:286)
at java.io.BufferedInputStream.read(BufferedInputStream.java:345)
- locked <0x000716426228> (a java.io.BufferedInputStream)
at 
org.apache.thrift.transport.TIOStreamTransport.read(TIOStreamTransport.java:127)
at org.apache.thrift.transport.TTransport.readAll(TTransport.java:84)
at 
org.apache.thrift.transport.TSaslTransport.receiveSaslMessage(TSaslTransport.java:178)
at 
org.apache.thrift.transport.TSaslTransport.open(TSaslTransport.java:288)
at 
org.apache.thrift.transport.TSaslClientTransport.open(TSaslClientTransport.java:37)
at 
org.apache.hive.jdbc.HiveConnection.openTransport(HiveConnection.java:157)
{code}


was (Author: azeroth2b):
(Hive 0.11)
Updating for CUSTOM authentication:


{code:title=Debug Output|borderStyle=solid}
16/09/08 09:36:48 DEBUG TSaslTransport: opening transport 
org.apache.thrift.transpor58
16/09/08 09:36:48 DEBUG TSaslClientTransport: Sending mechanism name PLAIN and 
initi
16/09/08 09:36:48 DEBUG TSaslTransport: CLIENT: Writing message with status 
START an
16/09/08 09:36:48 DEBUG TSaslTransport: CLIENT: Writing message with status 
COMPLETE
16/09/08 09:36:48 DEBUG TSaslTransport: CLIENT: Start message handled
16/09/08 09:36:48 DEBUG TSaslTransport: CLIENT: Main negotiation loop complete
16/09/08 09:36:48 DEBUG TSaslTransport: CLIENT: SASL Client receiving last 
message
{code}

{code:title=Partial Stack Trace|borderStyle=solid}
"main" #1 prio=5 os_prio=0 tid=0x0049f800 nid=0x409c runnable 
[0x0024d000]
   java.lang.Thread.State: RUNNABLE
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.socketRead(SocketInputStream.java:116)
at java.net.SocketInputStream.read(SocketInputStream.java:170)
at java.net.SocketInputStream.read(SocketInputStream.java:141)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:246)
at java.io.BufferedInputStream.read1(BufferedInputStream.java:286)
at java.io.BufferedInputStream.read(BufferedInputStream.java:345)
- locked <0x000716426228> (a java.io.BufferedInputStream)
at 
org.apache.thrift.transport.TIOStreamTransport.read(TIOStreamTransport.java:127)
at org.apache.thrift.transport.TTransport.readAll(TTransport.java:84)
at 
org.apache.thrift.transport.TSaslTransport.receiveSaslMessage(TSaslTransport.java:178)
at 
org.apache.thrift.transport.TSaslTransport.open(TSaslTransport.java:288)
at 
org.apache.thrift.transport.TSaslClientTransport.open(TSaslClientTransport.java:37)
at 
org.apache.hive.jdbc.HiveConnection.openTransport(HiveConnection.java:157)
{code}

> JDBC client connections hang at TSaslTransport
> --
>
> Key: HIVE-6852
> URL: https://issues.apache.org/jira/browse/HIVE-6852
> Project: Hive
>  Issue Type: Bug
>  Components: JDBC
>Reporter: jay vyas
>
> I've noticed that when there is an underlying issue in connecting a client to 
> the JDBC interface of the HiveServer2 to run queries, you get a hang after 
> the thrift portion, at least in certain scenarios: 
> Turning log4j to DEBUG, you

[jira] [Issue Comment Deleted] (HIVE-6852) JDBC client connections hang at TSaslTransport

2016-09-08 Thread Shawn Lavelle (JIRA) 

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

Shawn Lavelle updated HIVE-6852:

Comment: was deleted

(was: Any thoughts on this being a known JDK issue?
https://bugs.openjdk.java.net/browse/JDK-8049846
https://bugs.openjdk.java.net/browse/JDK-8075484)

> JDBC client connections hang at TSaslTransport
> --
>
> Key: HIVE-6852
> URL: https://issues.apache.org/jira/browse/HIVE-6852
> Project: Hive
>  Issue Type: Bug
>  Components: JDBC
>Reporter: jay vyas
>
> I've noticed that when there is an underlying issue in connecting a client to 
> the JDBC interface of the HiveServer2 to run queries, you get a hang after 
> the thrift portion, at least in certain scenarios: 
> Turning log4j to DEBUG, you can see the following when trying to get a 
> connection using:
> {noformat}
> Connection jdbc = 
> DriverManager.getConnection(this.con,"hive","password");
> "jdbc:hive2://localhost:1/default",
> {noformat}
> The logs get to here before the hang :
> {noformat}
> 0[main] DEBUG org.apache.thrift.transport.TSaslTransport  - opening 
> transport org.apache.thrift.transport.TSaslClientTransport@219ba640
> 0 [main] DEBUG org.apache.thrift.transport.TSaslTransport  - opening 
> transport org.apache.thrift.transport.TSaslClientTransport@219ba640
> 3[main] DEBUG org.apache.thrift.transport.TSaslClientTransport  - Sending 
> mechanism name PLAIN and initial response of length 14
> 3 [main] DEBUG org.apache.thrift.transport.TSaslClientTransport  - Sending 
> mechanism name PLAIN and initial response of length 14
> 5[main] DEBUG org.apache.thrift.transport.TSaslTransport  - CLIENT: 
> Writing message with status START and payload length 5
> 5 [main] DEBUG org.apache.thrift.transport.TSaslTransport  - CLIENT: Writing 
> message with status START and payload length 5
> 5[main] DEBUG org.apache.thrift.transport.TSaslTransport  - CLIENT: 
> Writing message with status COMPLETE and payload length 14
> 5 [main] DEBUG org.apache.thrift.transport.TSaslTransport  - CLIENT: Writing 
> message with status COMPLETE and payload length 14
> 5[main] DEBUG org.apache.thrift.transport.TSaslTransport  - CLIENT: Start 
> message handled
> 5 [main] DEBUG org.apache.thrift.transport.TSaslTransport  - CLIENT: Start 
> message handled
> 5[main] DEBUG org.apache.thrift.transport.TSaslTransport  - CLIENT: Main 
> negotiation loop complete
> 5 [main] DEBUG org.apache.thrift.transport.TSaslTransport  - CLIENT: Main 
> negotiation loop complete
> 6[main] DEBUG org.apache.thrift.transport.TSaslTransport  - CLIENT: SASL 
> Client receiving last message
> 6 [main] DEBUG org.apache.thrift.transport.TSaslTransport  - CLIENT: SASL 
> Client receiving last message
> {noformat}



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

[jira] [Comment Edited] (HIVE-6852) JDBC client connections hang at TSaslTransport

2016-09-08 Thread Shawn Lavelle (JIRA) 

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

Shawn Lavelle edited comment on HIVE-6852 at 9/8/16 2:44 PM:
-

(SHARK 0.9.1, Hive 0.11)
Updating for CUSTOM authentication:

Debug Output
{quote}
16/09/08 09:36:48 DEBUG TSaslTransport: opening transport 
org.apache.thrift.transpor58
16/09/08 09:36:48 DEBUG TSaslClientTransport: Sending mechanism name PLAIN and 
initi
16/09/08 09:36:48 DEBUG TSaslTransport: CLIENT: Writing message with status 
START an
16/09/08 09:36:48 DEBUG TSaslTransport: CLIENT: Writing message with status 
COMPLETE
16/09/08 09:36:48 DEBUG TSaslTransport: CLIENT: Start message handled
16/09/08 09:36:48 DEBUG TSaslTransport: CLIENT: Main negotiation loop complete
16/09/08 09:36:48 DEBUG TSaslTransport: CLIENT: SASL Client receiving last 
message
{quote}

Partial Stack Trace
{quote}
"main" #1 prio=5 os_prio=0 tid=0x0049f800 nid=0x409c runnable 
[0x0024d000]
   java.lang.Thread.State: RUNNABLE
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.socketRead(SocketInputStream.java:116)
at java.net.SocketInputStream.read(SocketInputStream.java:170)
at java.net.SocketInputStream.read(SocketInputStream.java:141)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:246)
at java.io.BufferedInputStream.read1(BufferedInputStream.java:286)
at java.io.BufferedInputStream.read(BufferedInputStream.java:345)
- locked <0x000716426228> (a java.io.BufferedInputStream)
at 
org.apache.thrift.transport.TIOStreamTransport.read(TIOStreamTransport.java:127)
at org.apache.thrift.transport.TTransport.readAll(TTransport.java:84)
at 
org.apache.thrift.transport.TSaslTransport.receiveSaslMessage(TSaslTransport.java:178)
at 
org.apache.thrift.transport.TSaslTransport.open(TSaslTransport.java:288)
at 
org.apache.thrift.transport.TSaslClientTransport.open(TSaslClientTransport.java:37)
at 
org.apache.hive.jdbc.HiveConnection.openTransport(HiveConnection.java:157)
{quote}


was (Author: azeroth2b):
Updating for CUSTOM authentication:

[code]
16/09/08 09:36:48 DEBUG TSaslTransport: opening transport 
org.apache.thrift.transpor58
16/09/08 09:36:48 DEBUG TSaslClientTransport: Sending mechanism name PLAIN and 
initi
16/09/08 09:36:48 DEBUG TSaslTransport: CLIENT: Writing message with status 
START an
16/09/08 09:36:48 DEBUG TSaslTransport: CLIENT: Writing message with status 
COMPLETE
16/09/08 09:36:48 DEBUG TSaslTransport: CLIENT: Start message handled
16/09/08 09:36:48 DEBUG TSaslTransport: CLIENT: Main negotiation loop complete
16/09/08 09:36:48 DEBUG TSaslTransport: CLIENT: SASL Client receiving last 
message
[/code]

Partial Stack Trace
[code]
"main" #1 prio=5 os_prio=0 tid=0x0049f800 nid=0x409c runnable 
[0x0024d000]
   java.lang.Thread.State: RUNNABLE
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.socketRead(SocketInputStream.java:116)
at java.net.SocketInputStream.read(SocketInputStream.java:170)
at java.net.SocketInputStream.read(SocketInputStream.java:141)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:246)
at java.io.BufferedInputStream.read1(BufferedInputStream.java:286)
at java.io.BufferedInputStream.read(BufferedInputStream.java:345)
- locked <0x000716426228> (a java.io.BufferedInputStream)
at 
org.apache.thrift.transport.TIOStreamTransport.read(TIOStreamTransport.java:127)
at org.apache.thrift.transport.TTransport.readAll(TTransport.java:84)
at 
org.apache.thrift.transport.TSaslTransport.receiveSaslMessage(TSaslTransport.java:178)
at 
org.apache.thrift.transport.TSaslTransport.open(TSaslTransport.java:288)
at 
org.apache.thrift.transport.TSaslClientTransport.open(TSaslClientTransport.java:37)
at 
org.apache.hive.jdbc.HiveConnection.openTransport(HiveConnection.java:157)
[/code]

> JDBC client connections hang at TSaslTransport
> --
>
> Key: HIVE-6852
> URL: https://issues.apache.org/jira/browse/HIVE-6852
> Project: Hive
>  Issue Type: Bug
>  Components: JDBC
>Reporter: jay vyas
>
> I've noticed that when there is an underlying issue in connecting a client to 
> the JDBC interface of the HiveServer2 to run queries, you get a hang after 
> the thrift portion, at least in certain scenarios: 
> Turning log4j to DEBUG, you can see the following when trying to get a 
> connection using:
> {noformat}
> Connection jdbc = 
> DriverManager.getConnection(this.con,"hive","password");
> "jdbc:hive2://localhost:1/default",
> {noformat}
> The logs get to here before the

[jira] [Comment Edited] (HIVE-6852) JDBC client connections hang at TSaslTransport

2016-09-08 Thread Shawn Lavelle (JIRA) 

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

Shawn Lavelle edited comment on HIVE-6852 at 9/8/16 2:47 PM:
-

(Hive 0.11)
Updating for CUSTOM authentication:


{code:title=Debug Output|borderStyle=solid}
16/09/08 09:36:48 DEBUG TSaslTransport: opening transport 
org.apache.thrift.transpor58
16/09/08 09:36:48 DEBUG TSaslClientTransport: Sending mechanism name PLAIN and 
initi
16/09/08 09:36:48 DEBUG TSaslTransport: CLIENT: Writing message with status 
START an
16/09/08 09:36:48 DEBUG TSaslTransport: CLIENT: Writing message with status 
COMPLETE
16/09/08 09:36:48 DEBUG TSaslTransport: CLIENT: Start message handled
16/09/08 09:36:48 DEBUG TSaslTransport: CLIENT: Main negotiation loop complete
16/09/08 09:36:48 DEBUG TSaslTransport: CLIENT: SASL Client receiving last 
message
{code}

{code:title=Partial Stack Trace|borderStyle=solid}
"main" #1 prio=5 os_prio=0 tid=0x0049f800 nid=0x409c runnable 
[0x0024d000]
   java.lang.Thread.State: RUNNABLE
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.socketRead(SocketInputStream.java:116)
at java.net.SocketInputStream.read(SocketInputStream.java:170)
at java.net.SocketInputStream.read(SocketInputStream.java:141)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:246)
at java.io.BufferedInputStream.read1(BufferedInputStream.java:286)
at java.io.BufferedInputStream.read(BufferedInputStream.java:345)
- locked <0x000716426228> (a java.io.BufferedInputStream)
at 
org.apache.thrift.transport.TIOStreamTransport.read(TIOStreamTransport.java:127)
at org.apache.thrift.transport.TTransport.readAll(TTransport.java:84)
at 
org.apache.thrift.transport.TSaslTransport.receiveSaslMessage(TSaslTransport.java:178)
at 
org.apache.thrift.transport.TSaslTransport.open(TSaslTransport.java:288)
at 
org.apache.thrift.transport.TSaslClientTransport.open(TSaslClientTransport.java:37)
at 
org.apache.hive.jdbc.HiveConnection.openTransport(HiveConnection.java:157)
{code}


was (Author: azeroth2b):
(SHARK 0.9.1, Hive 0.11)
Updating for CUSTOM authentication:


{code:title=Debug Output|borderStyle=solid}
16/09/08 09:36:48 DEBUG TSaslTransport: opening transport 
org.apache.thrift.transpor58
16/09/08 09:36:48 DEBUG TSaslClientTransport: Sending mechanism name PLAIN and 
initi
16/09/08 09:36:48 DEBUG TSaslTransport: CLIENT: Writing message with status 
START an
16/09/08 09:36:48 DEBUG TSaslTransport: CLIENT: Writing message with status 
COMPLETE
16/09/08 09:36:48 DEBUG TSaslTransport: CLIENT: Start message handled
16/09/08 09:36:48 DEBUG TSaslTransport: CLIENT: Main negotiation loop complete
16/09/08 09:36:48 DEBUG TSaslTransport: CLIENT: SASL Client receiving last 
message
{code}

{code:title=Partial Stack Trace|borderStyle=solid}
"main" #1 prio=5 os_prio=0 tid=0x0049f800 nid=0x409c runnable 
[0x0024d000]
   java.lang.Thread.State: RUNNABLE
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.socketRead(SocketInputStream.java:116)
at java.net.SocketInputStream.read(SocketInputStream.java:170)
at java.net.SocketInputStream.read(SocketInputStream.java:141)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:246)
at java.io.BufferedInputStream.read1(BufferedInputStream.java:286)
at java.io.BufferedInputStream.read(BufferedInputStream.java:345)
- locked <0x000716426228> (a java.io.BufferedInputStream)
at 
org.apache.thrift.transport.TIOStreamTransport.read(TIOStreamTransport.java:127)
at org.apache.thrift.transport.TTransport.readAll(TTransport.java:84)
at 
org.apache.thrift.transport.TSaslTransport.receiveSaslMessage(TSaslTransport.java:178)
at 
org.apache.thrift.transport.TSaslTransport.open(TSaslTransport.java:288)
at 
org.apache.thrift.transport.TSaslClientTransport.open(TSaslClientTransport.java:37)
at 
org.apache.hive.jdbc.HiveConnection.openTransport(HiveConnection.java:157)
{code}

> JDBC client connections hang at TSaslTransport
> --
>
> Key: HIVE-6852
> URL: https://issues.apache.org/jira/browse/HIVE-6852
> Project: Hive
>  Issue Type: Bug
>  Components: JDBC
>Reporter: jay vyas
>
> I've noticed that when there is an underlying issue in connecting a client to 
> the JDBC interface of the HiveServer2 to run queries, you get a hang after 
> the thrift portion, at least in certain scenarios: 
> Turning log4j to DEBUG, you can see the following when trying to get a 
> connection using:
> {noformat}
> Connection jdbc = 
>

[jira] [Comment Edited] (HIVE-6852) JDBC client connections hang at TSaslTransport

2016-09-08 Thread Shawn Lavelle (JIRA) 

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

Shawn Lavelle edited comment on HIVE-6852 at 9/8/16 2:38 PM:
-

This workaround doesn't work with authentication set to CUSTOM.  Client still 
hangs.


was (Author: azeroth2b):
This workaround doesn't seem to work with authentication set to CUSTOM.  Client 
still hangs.

> JDBC client connections hang at TSaslTransport
> --
>
> Key: HIVE-6852
> URL: https://issues.apache.org/jira/browse/HIVE-6852
> Project: Hive
>  Issue Type: Bug
>  Components: JDBC
>Reporter: jay vyas
>
> I've noticed that when there is an underlying issue in connecting a client to 
> the JDBC interface of the HiveServer2 to run queries, you get a hang after 
> the thrift portion, at least in certain scenarios: 
> Turning log4j to DEBUG, you can see the following when trying to get a 
> connection using:
> {noformat}
> Connection jdbc = 
> DriverManager.getConnection(this.con,"hive","password");
> "jdbc:hive2://localhost:1/default",
> {noformat}
> The logs get to here before the hang :
> {noformat}
> 0[main] DEBUG org.apache.thrift.transport.TSaslTransport  - opening 
> transport org.apache.thrift.transport.TSaslClientTransport@219ba640
> 0 [main] DEBUG org.apache.thrift.transport.TSaslTransport  - opening 
> transport org.apache.thrift.transport.TSaslClientTransport@219ba640
> 3[main] DEBUG org.apache.thrift.transport.TSaslClientTransport  - Sending 
> mechanism name PLAIN and initial response of length 14
> 3 [main] DEBUG org.apache.thrift.transport.TSaslClientTransport  - Sending 
> mechanism name PLAIN and initial response of length 14
> 5[main] DEBUG org.apache.thrift.transport.TSaslTransport  - CLIENT: 
> Writing message with status START and payload length 5
> 5 [main] DEBUG org.apache.thrift.transport.TSaslTransport  - CLIENT: Writing 
> message with status START and payload length 5
> 5[main] DEBUG org.apache.thrift.transport.TSaslTransport  - CLIENT: 
> Writing message with status COMPLETE and payload length 14
> 5 [main] DEBUG org.apache.thrift.transport.TSaslTransport  - CLIENT: Writing 
> message with status COMPLETE and payload length 14
> 5[main] DEBUG org.apache.thrift.transport.TSaslTransport  - CLIENT: Start 
> message handled
> 5 [main] DEBUG org.apache.thrift.transport.TSaslTransport  - CLIENT: Start 
> message handled
> 5[main] DEBUG org.apache.thrift.transport.TSaslTransport  - CLIENT: Main 
> negotiation loop complete
> 5 [main] DEBUG org.apache.thrift.transport.TSaslTransport  - CLIENT: Main 
> negotiation loop complete
> 6[main] DEBUG org.apache.thrift.transport.TSaslTransport  - CLIENT: SASL 
> Client receiving last message
> 6 [main] DEBUG org.apache.thrift.transport.TSaslTransport  - CLIENT: SASL 
> Client receiving last message
> {noformat}



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

[jira] [Commented] (HIVE-6852) JDBC client connections hang at TSaslTransport

2016-09-08 Thread Shawn Lavelle (JIRA) 

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

Shawn Lavelle commented on HIVE-6852:
-

Updating for CUSTOM authentication:

[code]
16/09/08 09:36:48 DEBUG TSaslTransport: opening transport 
org.apache.thrift.transpor58
16/09/08 09:36:48 DEBUG TSaslClientTransport: Sending mechanism name PLAIN and 
initi
16/09/08 09:36:48 DEBUG TSaslTransport: CLIENT: Writing message with status 
START an
16/09/08 09:36:48 DEBUG TSaslTransport: CLIENT: Writing message with status 
COMPLETE
16/09/08 09:36:48 DEBUG TSaslTransport: CLIENT: Start message handled
16/09/08 09:36:48 DEBUG TSaslTransport: CLIENT: Main negotiation loop complete
16/09/08 09:36:48 DEBUG TSaslTransport: CLIENT: SASL Client receiving last 
message
[/code]

Partial Stack Trace
[code]
"main" #1 prio=5 os_prio=0 tid=0x0049f800 nid=0x409c runnable 
[0x0024d000]
   java.lang.Thread.State: RUNNABLE
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.socketRead(SocketInputStream.java:116)
at java.net.SocketInputStream.read(SocketInputStream.java:170)
at java.net.SocketInputStream.read(SocketInputStream.java:141)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:246)
at java.io.BufferedInputStream.read1(BufferedInputStream.java:286)
at java.io.BufferedInputStream.read(BufferedInputStream.java:345)
- locked <0x000716426228> (a java.io.BufferedInputStream)
at 
org.apache.thrift.transport.TIOStreamTransport.read(TIOStreamTransport.java:127)
at org.apache.thrift.transport.TTransport.readAll(TTransport.java:84)
at 
org.apache.thrift.transport.TSaslTransport.receiveSaslMessage(TSaslTransport.java:178)
at 
org.apache.thrift.transport.TSaslTransport.open(TSaslTransport.java:288)
at 
org.apache.thrift.transport.TSaslClientTransport.open(TSaslClientTransport.java:37)
at 
org.apache.hive.jdbc.HiveConnection.openTransport(HiveConnection.java:157)
[/code]

> JDBC client connections hang at TSaslTransport
> --
>
> Key: HIVE-6852
> URL: https://issues.apache.org/jira/browse/HIVE-6852
> Project: Hive
>  Issue Type: Bug
>  Components: JDBC
>Reporter: jay vyas
>
> I've noticed that when there is an underlying issue in connecting a client to 
> the JDBC interface of the HiveServer2 to run queries, you get a hang after 
> the thrift portion, at least in certain scenarios: 
> Turning log4j to DEBUG, you can see the following when trying to get a 
> connection using:
> {noformat}
> Connection jdbc = 
> DriverManager.getConnection(this.con,"hive","password");
> "jdbc:hive2://localhost:1/default",
> {noformat}
> The logs get to here before the hang :
> {noformat}
> 0[main] DEBUG org.apache.thrift.transport.TSaslTransport  - opening 
> transport org.apache.thrift.transport.TSaslClientTransport@219ba640
> 0 [main] DEBUG org.apache.thrift.transport.TSaslTransport  - opening 
> transport org.apache.thrift.transport.TSaslClientTransport@219ba640
> 3[main] DEBUG org.apache.thrift.transport.TSaslClientTransport  - Sending 
> mechanism name PLAIN and initial response of length 14
> 3 [main] DEBUG org.apache.thrift.transport.TSaslClientTransport  - Sending 
> mechanism name PLAIN and initial response of length 14
> 5[main] DEBUG org.apache.thrift.transport.TSaslTransport  - CLIENT: 
> Writing message with status START and payload length 5
> 5 [main] DEBUG org.apache.thrift.transport.TSaslTransport  - CLIENT: Writing 
> message with status START and payload length 5
> 5[main] DEBUG org.apache.thrift.transport.TSaslTransport  - CLIENT: 
> Writing message with status COMPLETE and payload length 14
> 5 [main] DEBUG org.apache.thrift.transport.TSaslTransport  - CLIENT: Writing 
> message with status COMPLETE and payload length 14
> 5[main] DEBUG org.apache.thrift.transport.TSaslTransport  - CLIENT: Start 
> message handled
> 5 [main] DEBUG org.apache.thrift.transport.TSaslTransport  - CLIENT: Start 
> message handled
> 5[main] DEBUG org.apache.thrift.transport.TSaslTransport  - CLIENT: Main 
> negotiation loop complete
> 5 [main] DEBUG org.apache.thrift.transport.TSaslTransport  - CLIENT: Main 
> negotiation loop complete
> 6[main] DEBUG org.apache.thrift.transport.TSaslTransport  - CLIENT: SASL 
> Client receiving last message
> 6 [main] DEBUG org.apache.thrift.transport.TSaslTransport  - CLIENT: SASL 
> Client receiving last message
> {noformat}



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

[jira] [Commented] (HIVE-6852) JDBC client connections hang at TSaslTransport

2016-09-02 Thread Shawn Lavelle (JIRA) 

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

Shawn Lavelle commented on HIVE-6852:
-

This workaround doesn't seem to work with authentication set to CUSTOM.  Client 
still hangs.

> JDBC client connections hang at TSaslTransport
> --
>
> Key: HIVE-6852
> URL: https://issues.apache.org/jira/browse/HIVE-6852
> Project: Hive
>  Issue Type: Bug
>  Components: JDBC
>Reporter: jay vyas
>
> I've noticed that when there is an underlying issue in connecting a client to 
> the JDBC interface of the HiveServer2 to run queries, you get a hang after 
> the thrift portion, at least in certain scenarios: 
> Turning log4j to DEBUG, you can see the following when trying to get a 
> connection using:
> {noformat}
> Connection jdbc = 
> DriverManager.getConnection(this.con,"hive","password");
> "jdbc:hive2://localhost:1/default",
> {noformat}
> The logs get to here before the hang :
> {noformat}
> 0[main] DEBUG org.apache.thrift.transport.TSaslTransport  - opening 
> transport org.apache.thrift.transport.TSaslClientTransport@219ba640
> 0 [main] DEBUG org.apache.thrift.transport.TSaslTransport  - opening 
> transport org.apache.thrift.transport.TSaslClientTransport@219ba640
> 3[main] DEBUG org.apache.thrift.transport.TSaslClientTransport  - Sending 
> mechanism name PLAIN and initial response of length 14
> 3 [main] DEBUG org.apache.thrift.transport.TSaslClientTransport  - Sending 
> mechanism name PLAIN and initial response of length 14
> 5[main] DEBUG org.apache.thrift.transport.TSaslTransport  - CLIENT: 
> Writing message with status START and payload length 5
> 5 [main] DEBUG org.apache.thrift.transport.TSaslTransport  - CLIENT: Writing 
> message with status START and payload length 5
> 5[main] DEBUG org.apache.thrift.transport.TSaslTransport  - CLIENT: 
> Writing message with status COMPLETE and payload length 14
> 5 [main] DEBUG org.apache.thrift.transport.TSaslTransport  - CLIENT: Writing 
> message with status COMPLETE and payload length 14
> 5[main] DEBUG org.apache.thrift.transport.TSaslTransport  - CLIENT: Start 
> message handled
> 5 [main] DEBUG org.apache.thrift.transport.TSaslTransport  - CLIENT: Start 
> message handled
> 5[main] DEBUG org.apache.thrift.transport.TSaslTransport  - CLIENT: Main 
> negotiation loop complete
> 5 [main] DEBUG org.apache.thrift.transport.TSaslTransport  - CLIENT: Main 
> negotiation loop complete
> 6[main] DEBUG org.apache.thrift.transport.TSaslTransport  - CLIENT: SASL 
> Client receiving last message
> 6 [main] DEBUG org.apache.thrift.transport.TSaslTransport  - CLIENT: SASL 
> Client receiving last message
> {noformat}



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

[jira] [Commented] (HIVE-13824) NOSUCHMethodFound org.fusesource.jansi.internal.Kernel32.GetConsoleOutputCP()I

2016-06-16 Thread Shawn Lavelle (JIRA) 

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

Shawn Lavelle commented on HIVE-13824:
--

It's also in Maven.
http://mvnrepository.com/artifact/jline/jline

> NOSUCHMethodFound org.fusesource.jansi.internal.Kernel32.GetConsoleOutputCP()I
> --
>
> Key: HIVE-13824
> URL: https://issues.apache.org/jira/browse/HIVE-13824
> Project: Hive
>  Issue Type: Bug
>  Components: Beeline, Hive
> Environment: WIndows 8, HADOOP 2.7, HIVE 1.2.1, SPARK 1.6.1
>Reporter: Ekta Paliwal
>
> 0
> down vote
> favorite
> I have been trying to install hive on windows. I have 64 bit windows 8 on 
> which HADOOP and SPARK are running. I have
> 1.HADOOP_HOME
> 2.HIVE_HOME
> 3.SPARK_HOME
> 4.Platform
> 5.PATH
> all these variables set up on my system. Also, I was getting these error 
> before
> Missing Hive Execution Jar: 
> C:\hadoop1\hadoop-2.7.2\apache-hive-1.2.1-bin/lib/hive-exec-*.jar
> I solved these error by editing the Hive file inside bin folder of HIVE. 
> These errors are because of the forward slash"/" in environment variables in 
> HIVE file. I replace them with "\" and those errors are gone. But now I am 
> facing another problem. I am getting these error
> SLF4J: Class path contains multiple SLF4J bindings.
> SLF4J: Found binding in 
> [jar:file:/C:/spark/spark-1.6.1-bin-hadoop2.6/lib/spark-assembly-1.6.1-hadoop2.6.0.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: Found binding in 
> [jar:file:/C:/hadoop2.7/hadoop-2.7.1/share/hadoop/common/lib/slf4j-log4j12-1.7.10.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]
> Beeline version 1.6.1 by Apache Hive
> Exception in thread "main" java.lang.NoSuchMethodError: 
> org.fusesource.jansi.internal.Kernel32.GetConsoleOutputCP()I
> at 
> jline.WindowsTerminal.getConsoleOutputCodepage(WindowsTerminal.java:293)
> at jline.WindowsTerminal.getOutputEncoding(WindowsTerminal.java:186)
> at jline.console.ConsoleReader.(ConsoleReader.java:230)
> at jline.console.ConsoleReader.(ConsoleReader.java:221)
> at jline.console.ConsoleReader.(ConsoleReader.java:209)
> at org.apache.hive.beeline.BeeLine.getConsoleReader(BeeLine.java:834)
> at org.apache.hive.beeline.BeeLine.begin(BeeLine.java:770)
> at 
> org.apache.hive.beeline.BeeLine.mainWithInputRedirection(BeeLine.java:484)
> at org.apache.hive.beeline.BeeLine.main(BeeLine.java:467)
> 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)
> I have searched alot on these. Also I have posted these question on HIVE User 
> mailing List but got no response. Please help me with this. Not even getting 
> results when google this error.



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

[jira] [Comment Edited] (HIVE-13824) NOSUCHMethodFound org.fusesource.jansi.internal.Kernel32.GetConsoleOutputCP()I

2016-06-01 Thread Shawn Lavelle (JIRA) 

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

Shawn Lavelle edited comment on HIVE-13824 at 6/1/16 4:47 PM:
--

[~epaliwal] What resolved this for me was making sure I had the right version 
of jline in the classpath (2.12).


was (Author: azeroth2b):
What resolved this for me was making sure I had the right version of jline in 
the classpath (2.12).

> NOSUCHMethodFound org.fusesource.jansi.internal.Kernel32.GetConsoleOutputCP()I
> --
>
> Key: HIVE-13824
> URL: https://issues.apache.org/jira/browse/HIVE-13824
> Project: Hive
>  Issue Type: Bug
>  Components: Beeline, Hive
> Environment: WIndows 8, HADOOP 2.7, HIVE 1.2.1, SPARK 1.6.1
>Reporter: Ekta Paliwal
>
> 0
> down vote
> favorite
> I have been trying to install hive on windows. I have 64 bit windows 8 on 
> which HADOOP and SPARK are running. I have
> 1.HADOOP_HOME
> 2.HIVE_HOME
> 3.SPARK_HOME
> 4.Platform
> 5.PATH
> all these variables set up on my system. Also, I was getting these error 
> before
> Missing Hive Execution Jar: 
> C:\hadoop1\hadoop-2.7.2\apache-hive-1.2.1-bin/lib/hive-exec-*.jar
> I solved these error by editing the Hive file inside bin folder of HIVE. 
> These errors are because of the forward slash"/" in environment variables in 
> HIVE file. I replace them with "\" and those errors are gone. But now I am 
> facing another problem. I am getting these error
> SLF4J: Class path contains multiple SLF4J bindings.
> SLF4J: Found binding in 
> [jar:file:/C:/spark/spark-1.6.1-bin-hadoop2.6/lib/spark-assembly-1.6.1-hadoop2.6.0.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: Found binding in 
> [jar:file:/C:/hadoop2.7/hadoop-2.7.1/share/hadoop/common/lib/slf4j-log4j12-1.7.10.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]
> Beeline version 1.6.1 by Apache Hive
> Exception in thread "main" java.lang.NoSuchMethodError: 
> org.fusesource.jansi.internal.Kernel32.GetConsoleOutputCP()I
> at 
> jline.WindowsTerminal.getConsoleOutputCodepage(WindowsTerminal.java:293)
> at jline.WindowsTerminal.getOutputEncoding(WindowsTerminal.java:186)
> at jline.console.ConsoleReader.(ConsoleReader.java:230)
> at jline.console.ConsoleReader.(ConsoleReader.java:221)
> at jline.console.ConsoleReader.(ConsoleReader.java:209)
> at org.apache.hive.beeline.BeeLine.getConsoleReader(BeeLine.java:834)
> at org.apache.hive.beeline.BeeLine.begin(BeeLine.java:770)
> at 
> org.apache.hive.beeline.BeeLine.mainWithInputRedirection(BeeLine.java:484)
> at org.apache.hive.beeline.BeeLine.main(BeeLine.java:467)
> 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)
> I have searched alot on these. Also I have posted these question on HIVE User 
> mailing List but got no response. Please help me with this. Not even getting 
> results when google this error.



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

[jira] [Commented] (HIVE-13824) NOSUCHMethodFound org.fusesource.jansi.internal.Kernel32.GetConsoleOutputCP()I

2016-06-01 Thread Shawn Lavelle (JIRA) 

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

Shawn Lavelle commented on HIVE-13824:
--

What resolved this for me was making sure I had the right version of jline in 
the classpath (2.12).

> NOSUCHMethodFound org.fusesource.jansi.internal.Kernel32.GetConsoleOutputCP()I
> --
>
> Key: HIVE-13824
> URL: https://issues.apache.org/jira/browse/HIVE-13824
> Project: Hive
>  Issue Type: Bug
>  Components: Beeline, Hive
> Environment: WIndows 8, HADOOP 2.7, HIVE 1.2.1, SPARK 1.6.1
>Reporter: Ekta Paliwal
>
> 0
> down vote
> favorite
> I have been trying to install hive on windows. I have 64 bit windows 8 on 
> which HADOOP and SPARK are running. I have
> 1.HADOOP_HOME
> 2.HIVE_HOME
> 3.SPARK_HOME
> 4.Platform
> 5.PATH
> all these variables set up on my system. Also, I was getting these error 
> before
> Missing Hive Execution Jar: 
> C:\hadoop1\hadoop-2.7.2\apache-hive-1.2.1-bin/lib/hive-exec-*.jar
> I solved these error by editing the Hive file inside bin folder of HIVE. 
> These errors are because of the forward slash"/" in environment variables in 
> HIVE file. I replace them with "\" and those errors are gone. But now I am 
> facing another problem. I am getting these error
> SLF4J: Class path contains multiple SLF4J bindings.
> SLF4J: Found binding in 
> [jar:file:/C:/spark/spark-1.6.1-bin-hadoop2.6/lib/spark-assembly-1.6.1-hadoop2.6.0.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: Found binding in 
> [jar:file:/C:/hadoop2.7/hadoop-2.7.1/share/hadoop/common/lib/slf4j-log4j12-1.7.10.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]
> Beeline version 1.6.1 by Apache Hive
> Exception in thread "main" java.lang.NoSuchMethodError: 
> org.fusesource.jansi.internal.Kernel32.GetConsoleOutputCP()I
> at 
> jline.WindowsTerminal.getConsoleOutputCodepage(WindowsTerminal.java:293)
> at jline.WindowsTerminal.getOutputEncoding(WindowsTerminal.java:186)
> at jline.console.ConsoleReader.(ConsoleReader.java:230)
> at jline.console.ConsoleReader.(ConsoleReader.java:221)
> at jline.console.ConsoleReader.(ConsoleReader.java:209)
> at org.apache.hive.beeline.BeeLine.getConsoleReader(BeeLine.java:834)
> at org.apache.hive.beeline.BeeLine.begin(BeeLine.java:770)
> at 
> org.apache.hive.beeline.BeeLine.mainWithInputRedirection(BeeLine.java:484)
> at org.apache.hive.beeline.BeeLine.main(BeeLine.java:467)
> 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)
> I have searched alot on these. Also I have posted these question on HIVE User 
> mailing List but got no response. Please help me with this. Not even getting 
> results when google this error.



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

[jira] [Commented] (HIVE-13824) NOSUCHMethodFound org.fusesource.jansi.internal.Kernel32.GetConsoleOutputCP()I

2016-05-31 Thread Shawn Lavelle (JIRA) 

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

Shawn Lavelle commented on HIVE-13824:
--

The jansi library is dependent upon MSFT Visual C++ 2008 Runtime Executables.

"Windows XP Users: The JNI library that JANSI uses depends on the "Microsoft 
Visual C++ 2008 SP1 Redistributable" You can get a free copy from MS at:
http://www.microsoft.com/en-us/download/details.aspx?displaylang=en=5582;

source: https://github.com/fusesource/jansi

If this is the only thing driving the requirement of this library, perhaps a 
workaround should be considered.

> NOSUCHMethodFound org.fusesource.jansi.internal.Kernel32.GetConsoleOutputCP()I
> --
>
> Key: HIVE-13824
> URL: https://issues.apache.org/jira/browse/HIVE-13824
> Project: Hive
>  Issue Type: Bug
>  Components: Beeline, Hive
> Environment: WIndows 8, HADOOP 2.7, HIVE 1.2.1, SPARK 1.6.1
>Reporter: Ekta Paliwal
>
> 0
> down vote
> favorite
> I have been trying to install hive on windows. I have 64 bit windows 8 on 
> which HADOOP and SPARK are running. I have
> 1.HADOOP_HOME
> 2.HIVE_HOME
> 3.SPARK_HOME
> 4.Platform
> 5.PATH
> all these variables set up on my system. Also, I was getting these error 
> before
> Missing Hive Execution Jar: 
> C:\hadoop1\hadoop-2.7.2\apache-hive-1.2.1-bin/lib/hive-exec-*.jar
> I solved these error by editing the Hive file inside bin folder of HIVE. 
> These errors are because of the forward slash"/" in environment variables in 
> HIVE file. I replace them with "\" and those errors are gone. But now I am 
> facing another problem. I am getting these error
> SLF4J: Class path contains multiple SLF4J bindings.
> SLF4J: Found binding in 
> [jar:file:/C:/spark/spark-1.6.1-bin-hadoop2.6/lib/spark-assembly-1.6.1-hadoop2.6.0.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: Found binding in 
> [jar:file:/C:/hadoop2.7/hadoop-2.7.1/share/hadoop/common/lib/slf4j-log4j12-1.7.10.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]
> Beeline version 1.6.1 by Apache Hive
> Exception in thread "main" java.lang.NoSuchMethodError: 
> org.fusesource.jansi.internal.Kernel32.GetConsoleOutputCP()I
> at 
> jline.WindowsTerminal.getConsoleOutputCodepage(WindowsTerminal.java:293)
> at jline.WindowsTerminal.getOutputEncoding(WindowsTerminal.java:186)
> at jline.console.ConsoleReader.(ConsoleReader.java:230)
> at jline.console.ConsoleReader.(ConsoleReader.java:221)
> at jline.console.ConsoleReader.(ConsoleReader.java:209)
> at org.apache.hive.beeline.BeeLine.getConsoleReader(BeeLine.java:834)
> at org.apache.hive.beeline.BeeLine.begin(BeeLine.java:770)
> at 
> org.apache.hive.beeline.BeeLine.mainWithInputRedirection(BeeLine.java:484)
> at org.apache.hive.beeline.BeeLine.main(BeeLine.java:467)
> 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)
> I have searched alot on these. Also I have posted these question on HIVE User 
> mailing List but got no response. Please help me with this. Not even getting 
> results when google this error.



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

[jira] [Commented] (HIVE-1955) Support non-constant expressions for array indexes.

2016-02-26 Thread Shawn Lavelle (JIRA) 

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

Shawn Lavelle commented on HIVE-1955:
-

Was this ever addressed?

> Support non-constant expressions for array indexes.
> ---
>
> Key: HIVE-1955
> URL: https://issues.apache.org/jira/browse/HIVE-1955
> Project: Hive
>  Issue Type: Improvement
>Reporter: Adam Kramer
>Assignee: Navis
> Fix For: 0.14.0
>
>
> FAILED: Error in semantic analysis: line 4:8 Non Constant Expressions for 
> Array Indexes not Supported dut
> ...just wrote my own UDF to do this, and it is trivial. We should support 
> this natively.
> Let foo have these rows:
> arr   i
> [1,2,3]   1
> [3,4,5]   2
> [5,4,3]   2
> [0,0,1]   0
> Then,
> SELECT arr[i] FROM foo
> should return:
> 2
> 5
> 3
> 1
> Similarly, for the same table,
> SELECT 3 IN arr FROM foo
> should return:
> true
> true
> true
> false
> ...these use cases are needless limitations of functionality. We shouldn't 
> need UDFs to accomplish these goals.



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

[jira] [Commented] (HIVE-10399) from_unixtime_millis() Hive UDF

2016-02-19 Thread Shawn Lavelle (JIRA) 

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

Shawn Lavelle commented on HIVE-10399:
--

[~aihuaxu] Ahh, sure, that'll do it.  Available in Hive 1.2.0, and I'm on an 
older version for now. Thank you!

> from_unixtime_millis() Hive UDF
> ---
>
> Key: HIVE-10399
> URL: https://issues.apache.org/jira/browse/HIVE-10399
> Project: Hive
>  Issue Type: New Feature
>  Components: UDF
> Environment: HDP 2.2
>Reporter: Hari Sekhon
>Priority: Minor
>
> Feature request for a
> {code}from_unixtime_millis(){code}
> Hive UDF - from_unixtime() accepts only secs since epoch, and right now the 
> solution is to create a custom UDF, but this seems like quite a standard 
> thing to support millisecond precision dates in Hive natively.
> Hari Sekhon
> http://www.linkedin.com/in/harisekhon



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

[jira] [Commented] (HIVE-10399) from_unixtime_millis() Hive UDF

2016-02-19 Thread Shawn Lavelle (JIRA) 

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

Shawn Lavelle commented on HIVE-10399:
--

[~aihuaxu] That solves [~harisekhon]'s problem, but what if you want to custom 
format a millisecond timestamp similarly to from_unixtime()?  

> from_unixtime_millis() Hive UDF
> ---
>
> Key: HIVE-10399
> URL: https://issues.apache.org/jira/browse/HIVE-10399
> Project: Hive
>  Issue Type: New Feature
>  Components: UDF
> Environment: HDP 2.2
>Reporter: Hari Sekhon
>Priority: Minor
>
> Feature request for a
> {code}from_unixtime_millis(){code}
> Hive UDF - from_unixtime() accepts only secs since epoch, and right now the 
> solution is to create a custom UDF, but this seems like quite a standard 
> thing to support millisecond precision dates in Hive natively.
> Hari Sekhon
> http://www.linkedin.com/in/harisekhon



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