That's an older version of the HCatalog javadocs. You can find current
javadocs here: http://hive.apache.org/javadocs/r0.13.1/api/index.html.
-- Lefty
On Sun, Oct 12, 2014 at 3:05 PM, Suhas Gogate wrote:
> Edward/Hanish, this is a reasonable use case to justify Java API. I
> initially thought
Edward/Hanish, this is a reasonable use case to justify Java API. I
initially thought need for Java API to avoid knowing SQL :) but that you
can't for any DML operations :) So I guess for DDL operations you should
transition to HCatalog API.. See the design document where first para
explicitly adv
Thanks all for response !!
Totally agreed with Edward.
Also the reason why we don't want to use jdbc client is: Writing sql
statement for everything is little bit complex rather than calling direct
java apis.
With java metastore client api it was quite easy.
Regards,
Hanish
On 12/10/2014 2:25 a
Actually I do not love the jdbc api for all things.
I used to have several scripts that looped over all database, all tables,
and looked at specific meta store properties or locations. These scripts
were very small and to the point sometimes 5 line loops. Now I have to
write things like this:
Res
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
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.
--Su
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 (ja
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 thr
