Fwd: Pro and Cons of using HBase table as an external table in HIVE

Sorry. Need to send via right email address. Begin forwarded message: From: Michael Segel mailto:mse...@segel.com>> Subject: Re: Pro and Cons of using HBase table as an external table in HIVE Date: June 9, 2017 at 7:37:22 AM CDT To: user@hive.apache.org Hey Edward,

Re: Pro and Cons of using HBase table as an external table in HIVE

No. First, I apologize for my first response. I guess its never a good idea to check email at 4:00 in the morning before your first cup of coffee. ;-) I went into a bit more detail that may have confused the issue. To answer your question… In other words Is querying over plain hive (ORC or Text

Re: Pro and Cons of using HBase table as an external table in HIVE

Think about it like this one system is scanning a local file ORC, using an hbase scanner (over the network), and scanning the data in sstable format? On Fri, Jun 9, 2017 at 5:50 AM, Amey Barve wrote: > Hi Michael, > > "If there is predicate pushdown, then you will be faster, assuming that > the

Re: Pro and Cons of using HBase table as an external table in HIVE

Hi Michael, "If there is predicate pushdown, then you will be faster, assuming that the query triggers an implied range scan" ---> Does this bring results faster than plain hive querying over ORC / Text file formats In other words Is querying over plain hive (ORC or Text) *always* faster than thr

Re: Pro and Cons of using HBase table as an external table in HIVE

The pro’s is that you have the ability to update a table without having to worry about duplication of the row. Tez is doing some form of compaction for you that already exists in HBase. The cons: 1) Its slower. Reads from HBase have more overhead with them than just reading a file. Read Lar