Re: beeline remote client not connecting to hiveserver2

2014-07-10 Thread D K
What do you see in your hiveserver2 logs? There might be a clue there. On Thu, Jul 10, 2014 at 1:17 PM, Hang Chan wrote: > I tried using the username and password but still getting the same error. > > # hive --service beeline --verbose=true -u jdbc:hive2://hiveservice:11000 > -n root -p foo >

Re: beeline remote client not connecting to hiveserver2

2014-07-10 Thread Hang Chan
I tried using the username and password but still getting the same error. # hive --service beeline --verbose=true -u jdbc:hive2://hiveservice:11000 -n root -p foo issuing: !connect jdbc:hive2://hiveservice:11000 root foo scan complete in 36ms Connecting to jdbc:hive2://hiveservice:11000 Error: Inv

Re: beeline remote client not connecting to hiveserver2

2014-07-10 Thread D K
Oh, somewhere in the email thread I thought http transport mode was being used. If that's not the case then you should be able to login using: hive --service beeline -u jdbc:hive2://hiveservice:11000 -n $USER -p fakepwd Even though it doesn't do authentication, hiveserver2 still needs to a usernam

Re: beeline remote client not connecting to hiveserver2

2014-07-10 Thread Hang Chan
Nope, still not working. I don't believe I have http enabled. # hive --service beeline --verbose=true -u "jdbc:hive2://hiveservice:10001/default?hive.server2.transport.mode=http;hive.server2.thrift.http.path=cliservice" issuing: !connect jdbc:hive2://hiveservice:10001/default?hive.server2.transpo

Re: beeline remote client not connecting to hiveserver2

2014-07-07 Thread D K
How about try this? hive --service beeline -u jdbc:hive2://hiveservice:10001/default?hive.server2.transport.mode=http;hive.server2.thrift.http.path=cliservice In your previous response I see that you have "hive.server2.thrift.http.port=10001" On Thu, Jul 3, 2014 at 5:15 AM, Hang Chan wrote: >

Re: beeline remote client not connecting to hiveserver2

2014-07-03 Thread Hang Chan
It just stays stuck when I try to connect using http transport mode. [hiveclient]# hive --service beeline -u jdbc:hive2://hiveservice:11000/default?hive.server2.transport.mode=http;hive.server2.thrift.http.path=cliservice scan complete in 3ms Connecting to jdbc:hive2://hiveservice:11000/default?hi

Re: beeline remote client not connecting to hiveserver2

2014-07-02 Thread Andre Araujo
Does this work? jdbc:hive2://hiveservice:11000/default?hive.server2.transport.mode=http;hive.server2.thrift.http.path=cliservice Are you certain that HiveServer2 daemon is running on hiveservice AND listening on port 11000? On 3 July 2014 13:12, Hang Chan wrote: > hive.server.read.socket.tim

Re: beeline remote client not connecting to hiveserver2

2014-07-02 Thread Hang Chan
hive.server.read.socket.timeout=10 hive.server.tcp.keepalive=true hive.server2.async.exec.shutdown.timeout=10 hive.server2.async.exec.threads=50 hive.server2.authentication=NONE hive.server2.enable.doAs=true hive.server2.table.type.mapping=CLASSIC hive.server2.thrift.http.max.worker.threads=500 hiv

Re: beeline remote client not connecting to hiveserver2

2014-07-02 Thread Andre Araujo
Did you explicitly change the HiveServer2 port to 11000? The default is 1. Can you provide the output of the following ? hive -e set | grep hive.server On 3 July 2014 11:08, Hang Chan wrote: > It's not a dns problem. I just substituted my real server name with > "hiveservice". I confir

Re: beeline remote client not connecting to hiveserver2

2014-07-02 Thread Hang Chan
It's not a dns problem. I just substituted my real server name with "hiveservice". I confirmed that the hostname is indeed resolvable in dns. I also tried using the ip address in place of the hostname and I still get the same error. On Wed, Jul 2, 2014 at 5:36 PM, Andre Araujo wrote: > If th

Re: beeline remote client not connecting to hiveserver2

2014-07-02 Thread Andre Araujo
If the name "hiveserver" is not resolved correctly, that's the exact error you'd getting. Does "nslookup hiveservice" resolve the name successfully? Try using the fully qualified name instead. On 3 July 2014 07:01, Szehon Ho wrote: > I believe you should be able to put in anything by default.

Re: beeline remote client not connecting to hiveserver2

2014-07-02 Thread Szehon Ho
I believe you should be able to put in anything by default. The hive jdbc url is of the form jdbc:hive2://:, is the url correct? Thanks, Szehon On Wed, Jul 2, 2014 at 10:16 AM, Hang Chan wrote: > beeline does not seem to be connecting remotely. It works if I connect > using the embedded clie

Re: beeline remote client not connecting to hiveserver2

2014-07-02 Thread Andre Araujo
Is the name "hiveservice" being resolved successfully? If there's a problem with the name resolution, that's the exact message you'd get. Does "nslookup hiveservice" resolve the name? Try using the fully qualified name instead. On 3 July 2014 03:16, Hang Chan wrote: > beeline does not seem to

beeline remote client not connecting to hiveserver2

2014-07-02 Thread Hang Chan
beeline does not seem to be connecting remotely. It works if I connect using the embedded client. I am using all the default configurations, except I configured my hiveserver2 thrift port to 11000. If I put in the database name after the port number, it will prompt me for a username and password