Shiv,
Both Hbase and Hive alone is not perfect fit for Datawarehouse application. We
have to use Hive and Hbase to feed into traditional datawarehouse application.
Hbase: Hbase is more update oriented. Insert / Update / Delete operation is
efficient in Hbase. But it doesn't perform well as Hive
So, I tracked down the problem. But, I'm curious as to why I got such
different behavior when selecting directly from the partition vs. selecting
from all partitions.
Context: my custom deserializer was returning null when it encountered an
unintelligible line (I saw this pattern in the contr
At the request of many, the call-for-papers deadline for Hadoop Summit has been
extended by two weeks to March 7th.
Also, please note that you only need to submit an abstract at this time. You
will have much more time to create your actual presentations.
Additional details are here: www.hadoops
4 Newbie questions:
1. Assuming we are ok with non-SQL access, would HBASE work as a store for
a datawarehouse?
Basically, why HIVE for a warehouse? Why not HBASE? I understand the
SQL interface to HIVE, but are there other reasons?
2. How is the HBASE data model different from Hive?
Big
/tmp it is! My bad — it was the one obvious place I omitted from my find/grep
statement. Thanks!
From: Matthew Byrd mailto:mb...@acunu.com>>
Reply-To: mailto:user@hive.apache.org>>
Date: Wed, 22 Feb 2012 11:54:09 +
To: mailto:user@hive.apache.org>>
Subject: Re: Custom SerDe -- tracking down
Hi Evan,
Did you look in your hive.log file?
Mine is found in /tmp/$USER/ ... usually where stack traces from hive cli
show up If I'm not mistaken.
Have you tried hooking up a debugger to hive yet also? I'm guessing this is
how you knew the null pointer was being thrown on deserialize?
what is actu
