directory-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From conflue...@apache.org
Subject [CONF] Apache Directory SandBox > HBase Prototype
Date Tue, 19 Jan 2010 23:32:00 GMT
<html>
<head>
    <base href="http://cwiki.apache.org/confluence">
            <link rel="stylesheet" href="/confluence/s/1519/1/5/_/styles/combined.css?spaceKey=DIRxSBOX&amp;forWysiwyg=true"
type="text/css">
    </head>
<body style="background-color: white" bgcolor="white">
<div id="pageContent">
<div id="notificationFormat">
<div class="wiki-content">
<div class="email">
     <h2><a href="http://cwiki.apache.org/confluence/display/DIRxSBOX/HBase+Prototype">HBase
Prototype</a></h2>
     <h4>Page <b>edited</b> by             <a href="http://cwiki.apache.org/confluence/display/~seelmann">Stefan
Seelmann</a>
    </h4>
     
          <br/>
     <div class="notificationGreySide">
         <h1><a name="HBasePrototype-HBasePrototype"></a>HBase Prototype</h1>

<p>This page describes a partition which stores data in <a href="http://hadoop.apache.org/hbase/"
rel="nofollow">Hadoop's HBase</a> database.</p>

<h2><a name="HBasePrototype-Introduction"></a>Introduction</h2>

<p>The HBase partition is implemented as <a href="/confluence/display/DIRxSRVx11/Xdbm+Partition+Design"
title="Xdbm Partition Design">XDBM Partition</a>. The main advantage to an implementation
of the simple Partition interface is that the powerful search engine can be used. However
instead of storing entries by their DN an hierarchical approach is used, inspired by <a
href="http://cwiki.apache.org/confluence/display/DIRxSRVx11/Xdbm+fast+modifyDn+proposal" rel="nofollow">http://cwiki.apache.org/confluence/display/DIRxSRVx11/Xdbm+fast+modifyDn+proposal</a>
and <a href="http://www.openldap.org/conf/odd-sfo-2003/howard-dev.pdf" rel="nofollow">http://www.openldap.org/conf/odd-sfo-2003/howard-dev.pdf</a>.</p>

<p>In contrast to the JDBM (or the LDIF) partition, the directory server (ApacheDS)
and the storage enging (HBase) don't run within the same JVM but are distributed over the
network and communicate via RPC calls. Hence it is important to reduce the communication between
ApacheDS and HBase to a minimum.</p>

<h2><a name="HBasePrototype-HBaseSchemaDesign"></a>HBase Schema Design</h2>

<p>The following format is used to illustrate the HBase table layout, timestamps are
omitted:</p>

<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
<pre class="code-java">
------------------------------------------------------------
| table name | family1              | family2              |
------------------------------------------------------------
| row1       | qualifier1 -&gt; value1 | qualifierA -&gt; valueA |
|            | qualifier2 -&gt; value2 | qualifierB -&gt; valueB |
------------------------------------------------------------
| row2       | qualifier1 -&gt; value1 | qualifierA -&gt; valueA |
|            | qualifier2 -&gt; value2 | qualifierB -&gt; valueB |
------------------------------------------------------------
</pre>
</div></div>

<h3><a name="HBasePrototype-MasterTable"></a>Master Table</h3>

<p>The master table stores the entries, one entry per row:</p>

<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
<pre class="code-java">
--------------------------------------------------------------------------------------------------
| master | treeInfo                              | upAttributes                          
       |
--------------------------------------------------------------------------------------------------
|   0    | sequence -&gt; 8216                      |                                
              |
--------------------------------------------------------------------------------------------------
|   1    | parentId -&gt; 0                         | objectClass0 -&gt; top     
                     |
|        | upRdn -&gt; o=sevenSeas                  | objectClass1 -&gt; organization
                 |
|        | normRdn -&gt; 2.5.4.10=sevenseas         | o0 -&gt; sevenSeas         
                     |
--------------------------------------------------------------------------------------------------
|   2    | parentId -&gt; 1                         | objectClass0 -&gt; top     
                     |
|        | upRdn -&gt; ou=people                    | objectClass1 -&gt; organizationalUnit
           |
|        | normRdn -&gt; 2.5.4.11=people            | ou0 -&gt; people           
                     |
--------------------------------------------------------------------------------------------------
|   3    | parentId -&gt; 1                         | objectClass0 -&gt; top     
                     |
|        | upRdn -&gt; ou=groups                    | objectClass1 -&gt; organizationalUnit
           |
|        | normRdn -&gt; 2.5.4.11=groups            | ou0 -&gt; groups           
                     |
--------------------------------------------------------------------------------------------------
|   6    | parentId -&gt; 2                         | objectClass0 -&gt; top     
                     |
|        | upRdn -&gt; cn=Horatio Hornblower        | objectClass1 -&gt; person  
                     |
|        | normRdn -&gt; 2.5.4.3=horatio hornblower | objectClass2 -&gt; organizationalPerson
         |
|        |                                       | objectClass3 -&gt; inetOrgPerson  
              |
|        |                                       | cn0 -&gt; Horatio Hornblower      
              |
|        |                                       | description0 -&gt; Capt. Horatio Hornblower,
R.N |
|        |                                       | givenName0 -&gt; Horatio          
              |
|        |                                       | sn0 -&gt; Hornblower              
              |
|        |                                       | uid0 -&gt; hhornblo               
              |
|        |                                       | mail0 -&gt; hhornblo@royalnavy.mod.uk
           |
|        |                                       | userPassword0 -&gt; &lt;bytes&gt;
                     |
--------------------------------------------------------------------------------------------------
| ...    |                                       |                                       
       |
--------------------------------------------------------------------------------------------------
</pre>
</div></div>

<p>The row key is a sequentially generated 8-byte long. An advantage of using longs
is compatibility with XDBM. A disadvantage is that sequential keys are not optimal for distributing
data and load balancing across data nodes.</p>

<p>The 'treeInfo' column family stores hierarchical information:</p>
<ul>
	<li>Column 'parentId' contains the row key of the parent entry.</li>
	<li>Column 'upRdn' contains the user provided local name, relative to the parent (normally
the RDN; the suffix DN for the context entry). It is used to reconstruct the entry's DN.</li>
	<li>Column 'normRdn' contains the normalized local name, relative to the parent (normally
the RDN; DN for the context entry). This is just an optimization for constructing the key
of the tree table in order to avoid RDN normalization (see below).</li>
</ul>


<p>The 'upAttributes' column family contains a map with all the attributes. </p>
<ul>
	<li>The attribute description (type+options) is used as column qualifier.</li>
	<li>HBase stores one value per column. There are several workarounds how to store multiple
values. When using serialization or JSON format it won't be possible to access one value at
a time. Hence each value is stored in its own column and an additional index is added to the
column qualifier. This way each value can be read and written separately.</li>
	<li>The additional index is a zero-based 4-byte signed integer. To reconstruct the
user provided attribute description the last 4 bytes needs to be removed from the column qualifier.</li>
	<li>The values are stored as byte[].</li>
</ul>


<p>The row with key '0' is a special row, it's the virtual root. Its column 'treeInfo:sequence'
contains the row key sequence number. HBase provides an atomic increment-and-get operation
to obtain the next key for a new entry.</p>

<p>To retrieve the DN of an entry by its ID the entry's RDN and parent ID must be fetched.
As long as the parent ID is greather than 0 this step must be repeated for all parents. The
DN is the result of all concatenated RDNs.</p>

<p>It would be also possible to determine the ID for an DN, however a full table scan
would be necessary. For this reason a second table is available.</p>

<p>The master table contains all information needed to restore the data: reference to
the parent, user provided RDN, and user provided attributes.</p>

<p>Alternatives and Improvements:</p>
<ul>
	<li>It would be possible to store the serialized form of the server entry instead of
the attributes.</li>
	<li>It would be possible to store the serialized form of the RDN to avoid parsing.</li>
	<li>Different kind of attributes could be stored in separate column families (e.g.
binary attributes).</li>
	<li>Usage of entry UUID as row key. This helps to distribute the entries over all clusters
and may avoid hot spots.</li>
	<li>Add oneLevelCount and subLevelCount (currently stored in tree table) for faster
lookup of counts.</li>
	<li>Add normAttributes (currently stored in tree table) for faster lookup of reverse
index and evaluator.</li>
</ul>


     </div>
     <div id="commentsSection" class="wiki-content pageSection">
       <div style="float: right;">
            <a href="http://cwiki.apache.org/confluence/users/viewnotifications.action"
class="grey">Change Notification Preferences</a>
       </div>

       <a href="http://cwiki.apache.org/confluence/display/DIRxSBOX/HBase+Prototype">View
Online</a>
       |
       <a href="http://cwiki.apache.org/confluence/pages/diffpagesbyversion.action?pageId=9371750&revisedVersion=2&originalVersion=1">View
Change</a>
            </div>
</div>
</div>
</div>
</div>
</body>
</html>

Mime
View raw message