Good catch, Brett. Can we have confirmation from an expert?
Also, is object_type optional?
It isn't clear to me why priv_level isn't called object_name.
-- Lefty
On Thu, Oct 9, 2014 at 8:23 AM, Brett Randall wrote:
> Hi,
>
> On
> https://cwiki.apache.org/confluence/display/Hive/Hive+Default+
Arthur, there's a separate email address for subscribing to
u...@apache.hive.org -- see http://hive.apache.org/mailing_lists.html.
-- Lefty
On Sat, Oct 11, 2014 at 6:47 PM, arthur.hk.c...@gmail.com <
arthur.hk.c...@gmail.com> wrote:
> subscribe
>
Hi,
My Hive version is 0.13.1, I tried a smoke test, after 1 days 7 hours 5 minutes
19 seconds 70 msec, the job failed with error: Error: GC overhead limit exceeded
LOG:
2014-10-12 06:16:07,288 Stage-6 map = 100%, reduce = 50%, Cumulative CPU
425.35 sec
2014-10-12 06:16:12,431 Stage-6 map = 1
subscribe
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
