Srinivas, Can you please elaborate on why ODBC/JDBC is not an option ? I didn't understand what you meant by "unable to generate the HiveQL" with those options. How does using thrift api directly help in that case ?
ODBC/JDBC is the preferred API for users. There are many features implemented in those layers, including the security and also high availability features. Incorrect use of the thrift api can potentially lead to other issues like memory leaks in HiveServer2. On Wed, Dec 30, 2015 at 8:37 AM, Srinivas M <smudigo...@gmail.com> wrote: > Hi > > I am trying to develop a custom application using the Thrift Hive client > interface to access the Hive and read and write into the hive tables. ODBC > and JDBC are not option because of the inherent limitations with those > interfaces (i.e unable to generate the HiveQL etc). > > While using the Thrift Hive interface, the first challenge that I ran into > is with the authentication. I could able to connect to hive only when I set > the authentication of the hiveserver2 as NOSASL. > My application should be able to provide Kerberos authentication and all > other authentications supported by Hive. > > I had tried to look for some samples around implementing authentication in > the Thrift Hive client, but I could not find much details on that. > Can someone help me understand the options available for implementing > authentication while using the Thrift Hive client interfaces ? > > -- > Srinivas > (*-*) > ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ > You have to grow from the inside out. None can teach you, none can make you > spiritual. > -Narendra Nath Dutta(Swamy Vivekananda) > ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
