Hanish, I agree with Suhas and would strongly encourage you to use the JDBC API for HiveServer2. HiveServer2 has a thrift api for the client-server RPC, but that is *not* intended for end user consumption and could end up breaking your current code in future.
Is there any specific feature you are looking at which Hive's JDBC driver doesn't implement? Thanks, --Vaibhav On Sat, Oct 11, 2014 at 12:43 PM, Suhas Gogate <vgog...@pivotal.io> wrote: > Sorry Anish, but being database programmer in the past, I always used > embedded SQL interface... I was wondering should we really need direct Java > interface w/ HiveServer2? May be I am wrong, but would like to know your > view on what are the limitations of using embedded SQL vs direct Java API. > > --Suhas > > On Sat, Oct 11, 2014 at 12:38 PM, Suhas Gogate <vgog...@pivotal.io> wrote: > >> Hanish, this is interesting question and I also faced similar limitation >> lately. Although as Hive getting more closer to relational model with >> richer SQL interface (DDL/Authorization, DML) and HiveServer2 as a way to >> invoke embedded SQL in Java, the real question is should Hive Metastore >> Client (java) API should at all be used by user, rather all the existing >> Hive Client interfaces be talking to Hive Metastore internally? >> >> --Suhas >> >> >> >> On Fri, Oct 10, 2014 at 9:21 PM, Hanish Bansal < >> hanish.bansal.agar...@gmail.com> wrote: >> >>> Hi All, >>> >>> I am planning to use sql based authorization that is recently introduced >>> in hive 0.13.0. >>> >>> I was using hive metastore client java api early which has direct apis >>> for all operations like grant, revoke etc. >>> But for using new authorization I ll have to use hiveserver2 and pass >>> all requests through hiveserver2. I came up with JDBC client which can be >>> used to connect hiveserver2. The restriction there is we must have to write >>> SQL statements. >>> >>> I want to know is there any java api to connect hiveserver2, that have >>> direct java methods to perform operations and we don't need to write SQL >>> statements ?? >>> >>> Thanks, >>> Hanish >>> >> >> > -- 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.
