天天网官方

<bdo id="ug3eo"><b id="ug3eo"></b></bdo>

  • <tt id="ug3eo"><source id="ug3eo"><td id="ug3eo"></td></source></tt>
  • <bdo id="ug3eo"><input id="ug3eo"><p id="ug3eo"></p></input></bdo>

  • <bdo id="ug3eo"><b id="ug3eo"><tr id="ug3eo"></tr></b></bdo>

      March 10, 2015

      Notes on HBase

      I talked with a couple of Cloudera folks about HBase last week. Let me frame things by saying:

      Also:

      Cloudera’s views on HBase history — in response to the priorities I brought to the conversation — include:

      The HBase roadmap includes:

      Not on the HBase roadmap per se are global/secondary indexes. Rather, we talked about projects on top of HBase which are meant to provide those. One is Apache Phoenix, which supposedly:

      Another such project is Trafodion — supposedly the Welsh word for “transaction” — open sourced by HP. This seems to be based on NonStop SQL and Neoview code, which counter-intuitively have always been joined at the hip.

      There was a lot more to the conversation, but I’ll stop here for two reasons:

      Related link

      Comments

      4 Responses to “Notes on HBase”

      1. Jonathan Hsieh on March 11th, 2015 3:32 pm

        One minor point of clarification.

        Roughly 20% of our customers are HBase-focused and buy support only for HBase and core Hadoop. So, 20% choose the “flex” aka just-one component support level.

        Of the remaining 80% of customers, a similar percentage use HBase but in conjunction with other parts of the stack (Impala, Spark, etc) and thus choose the “EDH” or many component support level.

        – Jon

      2. More notes on HBase | DBMS?2 : DataBase Management System Services on March 17th, 2015 2:13 pm

        […] Continuing from last week’s HBase post, the Cloudera folks were fairly proud of HBase’s features for performance and scalability. […]

      3. Norbert Gergely on March 24th, 2015 5:55 am

        I would not ommit also Splice Machine from the list of relational DBMS on top of HBase. Mostly because they are claming to be
        – fully ACID
        – respecting ANSI SQL
        – using MVCC
        – highly concurential.
        What I miss is how well they are aknowledged and applied in the context of their commercial offer.

      4. Vladimir Rodionov on April 28th, 2015 12:49 am

        >> A kind of BLOB/CLOB (Binary/Character Large OBject) support

        That is because HDFS sucks at storing large number of small files. I am not the DB expert but think that storing blobs are usually delegated to a file system.

        Its not BLOB its BMOB actually (binary medium objects) to support storing digital pictures (not digital movies). This could be done w/o hacking HBase from inside – my humble opinion, but nevertheless, there is a strong support to include this feature into HBase.

      Leave a Reply




      Feed: DBMS (database management system), DW (data warehousing), BI (business intelligence), and analytics technology Subscribe to the Monash Research feed via RSS or email:

      Login

      Search our blogs and white papers

      Monash Research blogs

      User consulting

      Building a short list? Refining your strategic plan? We can help.

      Vendor advisory

      We tell vendors what's happening -- and, more important, what they should do about it.

      Monash Research highlights

      Learn about white papers, webcasts, and blog highlights, by RSS or email.

      <bdo id="ug3eo"><b id="ug3eo"></b></bdo>

    1. <tt id="ug3eo"><source id="ug3eo"><td id="ug3eo"></td></source></tt>
    2. <bdo id="ug3eo"><input id="ug3eo"><p id="ug3eo"></p></input></bdo>

    3. <bdo id="ug3eo"><b id="ug3eo"><tr id="ug3eo"></tr></b></bdo>

        大家赢即时比分

        360彩票官方网站

        亚盘 胜率

        真人在线博彩公司大全

        威尼斯人官方百家乐

        球探网即时足球比分

        pt老虎

        名人彩票官网

        彩客网彩票官网