What is your connection URL ? In case of Kerberos, it should be jdbc:hive2://<hostname>:<port>/<db>;principal=<HiveServer2-Principal>
thanks Prasad On Mon, Nov 3, 2014 at 1:16 AM, konark modi <modi.kon...@gmail.com> wrote: > Hi Vaibhav, > > Yes I have done that. I am on hive version. 0.12. > > But the same problem. > > Regards > Konark > On Nov 3, 2014 2:14 PM, "Vaibhav Gumashta" <vgumas...@hortonworks.com> > wrote: > >> Are you doing a kinit before launching beeline shell? Also what Hive >> version are you on? >> >> You need to do a kinit before you start using the beeline shell in a >> kerberized cluster setup. Kinit will essentially log the end user to >> Kerberos KDC, and set up the Kerberos TGT in the local system cache. >> >> Thanks, >> --Vaibhav >> >> On Mon, Nov 3, 2014 at 12:32 AM, konark modi <modi.kon...@gmail.com> >> wrote: >> >>> Hi All, >>> >>> I am running into a strange issue since last week. Would request your >>> help. >>> >>> I have a remote client from where in I ant to connect to hive via >>> beeline. >>> >>> I have two hadoop clusters one with kerberos authentication and other >>> without authentication. I am able to connect to HIVE which does not have >>> the authentication but running into problems when trying to connect to >>> cluster with kerberos authentication. >>> >>> On the contrary I am able to connect between the two clusters but not >>> from remote client. Please suggest what could be missing. >>> >>> >>> Installations & Logfile : >>> >>> 1. Remote client : yum install hadoop-client >>> 2. Log file : Remote client :http://pastebin.com/pUrY6i31 >>> HiveServer2 : http://pastebin.com/RNnbLv9f >>> >>> Regards >>> Konark Modi >>> >>> >> >> CONFIDENTIALITY NOTICE >> NOTICE: This message is intended for the use of the individual or entity >> to which it is addressed and may contain information that is confidential, >> privileged and exempt from disclosure under applicable law. If the reader >> of this message is not the intended recipient, you are hereby notified that >> any printing, copying, dissemination, distribution, disclosure or >> forwarding of this communication is strictly prohibited. If you have >> received this communication in error, please contact the sender immediately >> and delete it from your system. Thank You. > >
