Re: Hive metadata on Hbase

2016-10-23 Thread Per Ullberg
I thought the main gain was to get ACID on Hive performant enough. @Mich: Do you run with ACID-enabled tables? How many Create/Update/Deletes do you do per second? best regards /Pelle On Mon, Oct 24, 2016 at 7:39 AM, Jörn Franke wrote: > I think the main gain is more

Re: Hive metadata on Hbase

2016-10-23 Thread Jörn Franke
I think the main gain is more about getting rid of a dedicated database including maintenance and potential license cost. For really large clusters and a lot of users this might be even more beneficial. You can avoid clustering the database etc. > On 24 Oct 2016, at 00:46, Mich Talebzadeh

Hive metadata on Hbase

2016-10-23 Thread Mich Talebzadeh
A while back there was some notes on having Hive metastore on Hbase as opposed to conventional RDBMSs I am currently involved with some hefty work with Hbase and Phoenix for batch ingestion of trade data. As long as you define your Hbase table through Phoenix and with secondary Phoenix indexes on

Re: hiveserver2 GC overhead limit exceeded

2016-10-23 Thread Stephen Sprague
ok. i'll bite. lets see the output of this command where Hiveserver2 is running. $ ps -ef | grep -i hiveserver2 this'll show us all the command line parameters HS2 was (ultimately) invoked with. Cheers, Stephen On Sun, Oct 23, 2016 at 6:46 AM, patcharee wrote: >

hiveserver2 GC overhead limit exceeded

2016-10-23 Thread patcharee
Hi, I use beeline to connect to hiveserver2. I tested with a simple command and got an error GC overhead limit exceeded 0: jdbc:hive2://service-10-1:10010/default> drop table testhivedrivertable; Error: Error while processing statement: FAILED: Execution Error, return code 1 from