<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>question Re: Hive and Hbase : Which is best in terms of storage in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Hive-and-Hbase-Which-is-best-in-terms-of-storage/m-p/142090#M44122</link>
    <description>&lt;P&gt; I completely agree with josh.  hive is best suite for EDW type of querying.  HBase is a key value store, so you need to know your questions prior to designing the PDM.  Both use HDFS as the underlying storage.  If you which queries will be run and have a defined access path model, Phoenix/hbase will provide you lowest latency. If you are looking for general BI queries and can't define access path up front, hive is the way to go.&lt;/P&gt;</description>
    <pubDate>Fri, 21 Oct 2016 03:56:24 GMT</pubDate>
    <dc:creator>sunile_manjee</dc:creator>
    <dc:date>2016-10-21T03:56:24Z</dc:date>
    <item>
      <title>Hive and Hbase : Which is best in terms of storage</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Hive-and-Hbase-Which-is-best-in-terms-of-storage/m-p/142088#M44120</link>
      <description>&lt;P&gt;As both data resides on hdfs . So which is best in terms of Storage / Memory etc.&lt;/P&gt;</description>
      <pubDate>Fri, 21 Oct 2016 02:24:05 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Hive-and-Hbase-Which-is-best-in-terms-of-storage/m-p/142088#M44120</guid>
      <dc:creator>amit_dass</dc:creator>
      <dc:date>2016-10-21T02:24:05Z</dc:date>
    </item>
    <item>
      <title>Re: Hive and Hbase : Which is best in terms of storage</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Hive-and-Hbase-Which-is-best-in-terms-of-storage/m-p/142089#M44121</link>
      <description>&lt;P&gt;Apache Hive and Apache HBase are fundamentally different systems with completely different architectures. As such, which is most efficient really depends on the application use cases. It's impossible to generically state that Hive or HBase is better/worse than the other and the fact that they both use HDFS for storing data is irrelevant.&lt;/P&gt;&lt;P&gt;Please quantify the application requirements you have if you'd like an answer about whether Hive or HBase are better &lt;EM&gt;for you&lt;/EM&gt;.&lt;/P&gt;</description>
      <pubDate>Fri, 21 Oct 2016 02:34:47 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Hive-and-Hbase-Which-is-best-in-terms-of-storage/m-p/142089#M44121</guid>
      <dc:creator>elserj</dc:creator>
      <dc:date>2016-10-21T02:34:47Z</dc:date>
    </item>
    <item>
      <title>Re: Hive and Hbase : Which is best in terms of storage</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Hive-and-Hbase-Which-is-best-in-terms-of-storage/m-p/142090#M44122</link>
      <description>&lt;P&gt; I completely agree with josh.  hive is best suite for EDW type of querying.  HBase is a key value store, so you need to know your questions prior to designing the PDM.  Both use HDFS as the underlying storage.  If you which queries will be run and have a defined access path model, Phoenix/hbase will provide you lowest latency. If you are looking for general BI queries and can't define access path up front, hive is the way to go.&lt;/P&gt;</description>
      <pubDate>Fri, 21 Oct 2016 03:56:24 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Hive-and-Hbase-Which-is-best-in-terms-of-storage/m-p/142090#M44122</guid>
      <dc:creator>sunile_manjee</dc:creator>
      <dc:date>2016-10-21T03:56:24Z</dc:date>
    </item>
  </channel>
</rss>

