You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@hbase.apache.org by st...@apache.org on 2013/04/02 20:06:21 UTC
svn commit: r1463652 [18/21] - in /hbase/hbase.apache.org/trunk: ./ book/
case_studies/ community/ configuration/ css/ developer/ external_apis/
getting_started/ hbase-assembly/ hbase-assembly/book/ hbase-assembly/xref/
images/ ops_mgt/ performance/ pr...
Modified: hbase/hbase.apache.org/trunk/project-summary.html
URL: http://svn.apache.org/viewvc/hbase/hbase.apache.org/trunk/project-summary.html?rev=1463652&r1=1463651&r2=1463652&view=diff
==============================================================================
--- hbase/hbase.apache.org/trunk/project-summary.html (original)
+++ hbase/hbase.apache.org/trunk/project-summary.html Tue Apr 2 18:06:19 2013
@@ -1,167 +1,204 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<!-- Generated by Apache Maven Doxia Site Renderer 1.3 at Apr 2, 2013 -->
-<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
- <head>
- <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
- <title>HBase - Project Summary</title>
- <style type="text/css" media="all">
- @import url("./css/maven-base.css");
- @import url("./css/maven-theme.css");
- @import url("./css/site.css");
- </style>
- <link rel="stylesheet" href="./css/print.css" type="text/css" media="print" />
- <meta name="Date-Revision-yyyymmdd" content="20130402" />
- <meta http-equiv="Content-Language" content="en" />
-
- </head>
- <body class="composite">
- <div id="banner">
- <div id="bannerLeft">
- HBase
- </div>
- <div class="clear">
- <hr/>
- </div>
- </div>
- <div id="breadcrumbs">
-
-
- <div class="xleft">
- <span id="publishDate">Last Published: 2013-04-02</span>
- | <span id="projectVersion">Version: 0.97.0-SNAPSHOT</span>
- </div>
- <div class="xright"> <a href="./" title="HBase">HBase</a>
-
-
- </div>
- <div class="clear">
- <hr/>
- </div>
- </div>
- <div id="leftColumn">
- <div id="navcolumn">
-
-
- <h5>Modules</h5>
- <ul>
- <li class="none">
- <a href="hbase-server/index.html" title="HBase - Server">HBase - Server</a>
- </li>
- <li class="none">
- <a href="hbase-protocol/index.html" title="HBase - Protocol">HBase - Protocol</a>
- </li>
- <li class="none">
- <a href="hbase-client/index.html" title="HBase - Client">HBase - Client</a>
- </li>
- <li class="none">
- <a href="hbase-hadoop-compat/index.html" title="HBase - Hadoop Compatibility">HBase - Hadoop Compatibility</a>
- </li>
- <li class="none">
- <a href="hbase-common/index.html" title="HBase - Common">HBase - Common</a>
- </li>
- <li class="none">
- <a href="hbase-it/index.html" title="HBase - Integration Tests">HBase - Integration Tests</a>
- </li>
- <li class="none">
- <a href="hbase-examples/index.html" title="HBase - Examples">HBase - Examples</a>
- </li>
- <li class="none">
- <a href="hbase-prefix-tree/index.html" title="HBase - Prefix Tree">HBase - Prefix Tree</a>
- </li>
- <li class="none">
- <a href="hbase-assembly/index.html" title="HBase - Assembly">HBase - Assembly</a>
- </li>
- <li class="none">
- <a href="hbase-hadoop1-compat/index.html" title="HBase - Hadoop One Compatibility">HBase - Hadoop One Compatibility</a>
- </li>
- </ul>
- <h5>Project Documentation</h5>
- <ul>
- <li class="expanded">
- <a href="project-info.html" title="Project Information">Project Information</a>
- <ul>
- <li class="none">
- <a href="team-list.html" title="Project Team">Project Team</a>
- </li>
- <li class="none">
- <a href="mail-lists.html" title="Mailing Lists">Mailing Lists</a>
- </li>
- <li class="none">
- <a href="integration.html" title="Continuous Integration">Continuous Integration</a>
- </li>
- <li class="none">
- <a href="issue-tracking.html" title="Issue Tracking">Issue Tracking</a>
- </li>
- <li class="none">
- <a href="license.html" title="Project License">Project License</a>
- </li>
- <li class="none">
- <a href="source-repository.html" title="Source Repository">Source Repository</a>
- </li>
- <li class="none">
- <a href="index.html" title="About">About</a>
- </li>
- <li class="none">
- <strong>Project Summary</strong>
- </li>
- <li class="none">
- <a href="dependency-info.html" title="Dependency Information">Dependency Information</a>
- </li>
- <li class="none">
- <a href="modules.html" title="Project Modules">Project Modules</a>
- </li>
- <li class="none">
- <a href="dependency-management.html" title="Dependency Management">Dependency Management</a>
- </li>
- <li class="none">
- <a href="dependencies.html" title="Dependencies">Dependencies</a>
- </li>
- <li class="none">
- <a href="dependency-convergence.html" title="Dependency Convergence">Dependency Convergence</a>
- </li>
- <li class="none">
- <a href="plugin-management.html" title="Plugin Management">Plugin Management</a>
- </li>
- <li class="none">
- <a href="plugins.html" title="Project Plugins">Project Plugins</a>
- </li>
- <li class="none">
- <a href="distribution-management.html" title="Distribution Management">Distribution Management</a>
- </li>
- </ul>
- </li>
- <li class="collapsed">
- <a href="project-reports.html" title="Project Reports">Project Reports</a>
- </li>
- </ul>
- <a href="http://maven.apache.org/" title="Built by Maven" class="poweredBy">
- <img class="poweredBy" alt="Built by Maven" src="./images/logos/maven-feather.png" />
- </a>
-
-
- </div>
- </div>
- <div id="bodyColumn">
- <div id="contentBox">
- <div class="section"><h2>Project Summary<a name="Project_Summary"></a></h2><a name="Project_Summary"></a><div class="section"><h3>Project Information<a name="Project_Information"></a></h3><a name="Project_Information"></a><table border="0" class="bodyTable"><tr class="a"><th>Field</th><th>Value</th></tr><tr class="b"><td>Name</td><td>HBase</td></tr><tr class="a"><td>Description</td><td>Apache HBase™ is the Hadoop database. Use it when you need
- random, realtime read/write access to your Big Data.
- This project's goal is the hosting of very large tables -- billions of rows X millions of columns -- atop clusters
- of commodity hardware.</td></tr><tr class="b"><td>Homepage</td><td><a class="externalLink" href="http://hbase.apache.org">http://hbase.apache.org</a></td></tr></table></div><div class="section"><h3>Project Organization<a name="Project_Organization"></a></h3><a name="Project_Organization"></a><table border="0" class="bodyTable"><tr class="a"><th>Field</th><th>Value</th></tr><tr class="b"><td>Name</td><td>The Apache Software Foundation</td></tr><tr class="a"><td>URL</td><td><a class="externalLink" href="http://www.apache.org/">http://www.apache.org/</a></td></tr></table></div><div class="section"><h3>Build Information<a name="Build_Information"></a></h3><a name="Build_Information"></a><table border="0" class="bodyTable"><tr class="a"><th>Field</th><th>Value</th></tr><tr class="b"><td>GroupId</td><td>org.apache.hbase</td></tr><tr class="a"><td>ArtifactId</td><td>hbase</td></tr><tr class="b"><td>Version</td><td>0.97.0-SNAPSHOT</td></tr><tr class="a"><td>Type</td><td>pom</td>
</tr></table></div></div>
- </div>
- </div>
- <div class="clear">
- <hr/>
- </div>
- <div id="footer">
- <div class="xright">
- Copyright © 2013
- <a href="http://www.apache.org/">The Apache Software Foundation</a>.
- All Rights Reserved.
-
- </div>
- <div class="clear">
- <hr/>
- </div>
- </div>
- </body>
-</html>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+
+<!-- Generated by Apache Maven Doxia at Apr 2, 2013 -->
+<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
+ <head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
+ <title>HBase - Assembly - Project Summary</title>
+ <style type="text/css" media="all">
+ @import url("./css/maven-base.css");
+ @import url("./css/maven-theme.css");
+ @import url("./css/site.css");
+ </style>
+ <link rel="stylesheet" href="./css/print.css" type="text/css" media="print" />
+ <link rel="shortcut icon" href="/images/favicon.ico" />
+ <meta name="Date-Revision-yyyymmdd" content="20130402" />
+ <meta http-equiv="Content-Language" content="en" />
+ <!--Google Analytics-->
+<script type="text/javascript">
+
+ var _gaq = _gaq || [];
+ _gaq.push(['_setAccount', 'UA-30210968-1']);
+ _gaq.push(['_trackPageview']);
+
+ (function() {
+ var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;
+ ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js';
+ var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);
+ })();
+
+</script>
+ </head>
+ <body class="composite">
+ <div id="banner">
+ <a href="../" id="bannerLeft">
+ <img src="images/hbase_logo.png" alt="Apache HBase" />
+ </a>
+ <!-- Commented out since we do not use it. St.Ack 20110906
+ -->
+ <div class="clear">
+ <hr/>
+ </div>
+ </div>
+ <div id="breadcrumbs">
+ <div class="xright" style="padding-left: 8px; margin-top: -4px;">
+ <form method="GET" action="http://search-hadoop.com/">
+ <input type="text" style="width: 192px; height: 15px; font-size: inherit; border: 1px solid darkgray" name="q" value="Search wiki, mailing lists & more" onfocus="this.value=''"/>
+ <input type="hidden" name="fc_project" value="HBase"/>
+ <button style="height: 20px; width: 60px;">Search</button>
+ </form>
+ </div>
+ <div class="clear">
+ <hr/>
+ </div>
+ </div>
+ <div id="leftColumn">
+ <div id="navcolumn">
+
+
+ <h5>Apache HBase Project</h5>
+ <ul>
+ <li class="none">
+ <a href="index.html" title="Overview">Overview</a>
+ </li>
+ <li class="none">
+ <a href="license.html" title="License">License</a>
+ </li>
+ <li class="none">
+ <a href="http://www.apache.org/dyn/closer.cgi/hbase/" class="externalLink" title="Downloads">Downloads</a>
+ </li>
+ <li class="none">
+ <a href="https://issues.apache.org/jira/browse/HBASE?report=com.atlassian.jira.plugin.system.project:changelog-panel#selectedTab=com.atlassian.jira.plugin.system.project%3Achangelog-panel" class="externalLink" title="Release Notes">Release Notes</a>
+ </li>
+ <li class="none">
+ <a href="issue-tracking.html" title="Issue Tracking">Issue Tracking</a>
+ </li>
+ <li class="none">
+ <a href="mail-lists.html" title="Mailing Lists">Mailing Lists</a>
+ </li>
+ <li class="none">
+ <a href="source-repository.html" title="Source Repository">Source Repository</a>
+ </li>
+ <li class="none">
+ <a href="https://reviews.apache.org" class="externalLink" title="ReviewBoard">ReviewBoard</a>
+ </li>
+ <li class="none">
+ <a href="builds.apache.org" title="Apache Build Box">Apache Build Box</a>
+ </li>
+ <li class="none">
+ <a href="http://54.241.6.143/" class="externalLink" title="EC2 Build Box">EC2 Build Box</a>
+ </li>
+ <li class="none">
+ <a href="team-list.html" title="Team">Team</a>
+ </li>
+ <li class="none">
+ <a href="sponsors.html" title="Thanks">Thanks</a>
+ </li>
+ <li class="none">
+ <a href="http://blogs.apache.org/hbase/" class="externalLink" title="Blog">Blog</a>
+ </li>
+ <li class="none">
+ <a href="resources.html" title="Other resources">Other resources</a>
+ </li>
+ </ul>
+ <h5>Documentation</h5>
+ <ul>
+ <li class="none">
+ <a href="book/quickstart.html" title="Getting Started">Getting Started</a>
+ </li>
+ <li class="none">
+ <a href="apidocs/index.html" title="API">API</a>
+ </li>
+ <li class="none">
+ <a href="xref/index.html" title="X-Ref">X-Ref</a>
+ </li>
+ <li class="none">
+ <a href="book/book.html" title="Ref Guide (multi-page)">Ref Guide (multi-page)</a>
+ </li>
+ <li class="none">
+ <a href="book.html" title="Ref Guide (single-page)">Ref Guide (single-page)</a>
+ </li>
+ <li class="none">
+ <a href="http://abloz.com/hbase/book.html" class="externalLink" title="ä¸æåèæå(å页)">ä¸æåèæå(å页)</a>
+ </li>
+ <li class="none">
+ <a href="book/faq.html" title="FAQ">FAQ</a>
+ </li>
+ <li class="none">
+ <a href="book.html#other.info" title="Videos/Presentations">Videos/Presentations</a>
+ </li>
+ <li class="none">
+ <a href="http://wiki.apache.org/hadoop/Hbase" class="externalLink" title="Wiki">Wiki</a>
+ </li>
+ <li class="none">
+ <a href="acid-semantics.html" title="ACID Semantics">ACID Semantics</a>
+ </li>
+ <li class="none">
+ <a href="book.html#arch.bulk.load" title="Bulk Loads">Bulk Loads</a>
+ </li>
+ <li class="none">
+ <a href="metrics.html" title="Metrics">Metrics</a>
+ </li>
+ <li class="none">
+ <a href="cygwin.html" title="HBase on Windows">HBase on Windows</a>
+ </li>
+ <li class="none">
+ <a href="replication.html" title="Cluster replication">Cluster replication</a>
+ </li>
+ </ul>
+ <h5>0.94 Documentation</h5>
+ <ul>
+ <li class="none">
+ <a href="0.94/apidocs/index.html" title="API">API</a>
+ </li>
+ <li class="none">
+ <a href="0.94/xref/index.html" title="X-Ref">X-Ref</a>
+ </li>
+ <li class="none">
+ <a href="0.94/book.html" title="Ref Guide (single-page)">Ref Guide (single-page)</a>
+ </li>
+ </ul>
+ <h5>ASF</h5>
+ <ul>
+ <li class="none">
+ <a href="http://www.apache.org/foundation/" class="externalLink" title="Apache Software Foundation">Apache Software Foundation</a>
+ </li>
+ <li class="none">
+ <a href="http://www.apache.org/foundation/how-it-works.html" class="externalLink" title="How Apache Works">How Apache Works</a>
+ </li>
+ <li class="none">
+ <a href="http://www.apache.org/foundation/sponsorship.html" class="externalLink" title="Sponsoring Apache">Sponsoring Apache</a>
+ </li>
+ </ul>
+ <a href="http://maven.apache.org/" title="Built by Maven" class="poweredBy">
+ <img class="poweredBy" alt="Built by Maven" src="./images/logos/maven-feather.png" />
+ </a>
+
+
+ </div>
+ </div>
+ <div id="bodyColumn">
+ <div id="contentBox">
+ <div class="section"><h2>Project Summary<a name="Project_Summary"></a></h2><a name="Project_Summary"></a><div class="section"><h3>Project Information<a name="Project_Information"></a></h3><a name="Project_Information"></a><table border="0" class="bodyTable"><tr class="a"><th>Field</th><th>Value</th></tr><tr class="b"><td>Name</td><td>HBase - Assembly</td></tr><tr class="a"><td>Description</td><td>Module that does project assembly and site.</td></tr><tr class="b"><td>Homepage</td><td><a class="externalLink" href="http://hbase.apache.org/hbase-assembly">http://hbase.apache.org/hbase-assembly</a></td></tr></table></div><div class="section"><h3>Project Organization<a name="Project_Organization"></a></h3><a name="Project_Organization"></a><table border="0" class="bodyTable"><tr class="a"><th>Field</th><th>Value</th></tr><tr class="b"><td>Name</td><td>The Apache Software Foundation</td></tr><tr class="a"><td>URL</td><td><a class="externalLink" href="http://www.apache.org/"
>http://www.apache.org/</a></td></tr></table></div><div class="section"><h3>Build Information<a name="Build_Information"></a></h3><a name="Build_Information"></a><table border="0" class="bodyTable"><tr class="a"><th>Field</th><th>Value</th></tr><tr class="b"><td>GroupId</td><td>org.apache.hbase</td></tr><tr class="a"><td>ArtifactId</td><td>hbase-assembly</td></tr><tr class="b"><td>Version</td><td>0.97.0-SNAPSHOT</td></tr><tr class="a"><td>Type</td><td>pom</td></tr></table></div></div>
+ </div>
+ </div>
+ <div class="clear">
+ <hr/>
+ </div>
+ <div id="footer">
+ <div class="xright">
+
+ <span id="publishDate">Last Published: 2013-04-02</span>
+ | <span id="projectVersion">Version: 0.97.0-SNAPSHOT</span>
+
+ </div>
+ <div class="xright">Copyright ©<a href="http://www.apache.org"> 2013
+ <a href="http://www.apache.org/">The Apache Software Foundation</a>.
+ </a>All Rights Reserved. Apache Hadoop, Hadoop, HDFS, HBase and the HBase project logo are trademarks of the Apache Software Foundation.
+ </div>
+ <div class="clear">
+ <hr/>
+ </div>
+ </div>
+ </body>
+</html>
Modified: hbase/hbase.apache.org/trunk/pseudo-distributed.html
URL: http://svn.apache.org/viewvc/hbase/hbase.apache.org/trunk/pseudo-distributed.html?rev=1463652&r1=1463651&r2=1463652&view=diff
==============================================================================
--- hbase/hbase.apache.org/trunk/pseudo-distributed.html (original)
+++ hbase/hbase.apache.org/trunk/pseudo-distributed.html Tue Apr 2 18:06:19 2013
@@ -1,10 +1,10 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<!-- Generated by Apache Maven Doxia at Mar 29, 2013 -->
+<!-- Generated by Apache Maven Doxia at Apr 2, 2013 -->
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
- <title>HBase -
+ <title>HBase - Assembly -
Running Apache HBase (TM) in pseudo-distributed mode
</title>
@@ -15,7 +15,7 @@ Running Apache HBase (TM) in pseudo-dist
</style>
<link rel="stylesheet" href="./css/print.css" type="text/css" media="print" />
<link rel="shortcut icon" href="/images/favicon.ico" />
- <meta name="Date-Revision-yyyymmdd" content="20130329" />
+ <meta name="Date-Revision-yyyymmdd" content="20130402" />
<meta http-equiv="Content-Language" content="en" />
<!--Google Analytics-->
<script type="text/javascript">
@@ -34,7 +34,7 @@ Running Apache HBase (TM) in pseudo-dist
</head>
<body class="composite">
<div id="banner">
- <a href="./" id="bannerLeft">
+ <a href="../" id="bannerLeft">
<img src="images/hbase_logo.png" alt="Apache HBase" />
</a>
<!-- Commented out since we do not use it. St.Ack 20110906
@@ -86,6 +86,12 @@ Running Apache HBase (TM) in pseudo-dist
<a href="https://reviews.apache.org" class="externalLink" title="ReviewBoard">ReviewBoard</a>
</li>
<li class="none">
+ <a href="builds.apache.org" title="Apache Build Box">Apache Build Box</a>
+ </li>
+ <li class="none">
+ <a href="http://54.241.6.143/" class="externalLink" title="EC2 Build Box">EC2 Build Box</a>
+ </li>
+ <li class="none">
<a href="team-list.html" title="Team">Team</a>
</li>
<li class="none">
@@ -204,8 +210,8 @@ Running Apache HBase (TM) in pseudo-dist
<div id="footer">
<div class="xright">
- <span id="publishDate">Last Published: 2013-03-29</span>
- | <span id="projectVersion">Version: 0.97-SNAPSHOT</span>
+ <span id="publishDate">Last Published: 2013-04-02</span>
+ | <span id="projectVersion">Version: 0.97.0-SNAPSHOT</span>
</div>
<div class="xright">Copyright ©<a href="http://www.apache.org"> 2013
Modified: hbase/hbase.apache.org/trunk/replication.html
URL: http://svn.apache.org/viewvc/hbase/hbase.apache.org/trunk/replication.html?rev=1463652&r1=1463651&r2=1463652&view=diff
==============================================================================
--- hbase/hbase.apache.org/trunk/replication.html (original)
+++ hbase/hbase.apache.org/trunk/replication.html Tue Apr 2 18:06:19 2013
@@ -1,10 +1,10 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<!-- Generated by Apache Maven Doxia at Mar 29, 2013 -->
+<!-- Generated by Apache Maven Doxia at Apr 2, 2013 -->
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
- <title>HBase -
+ <title>HBase - Assembly -
Apache HBase (TM) Replication
</title>
@@ -15,7 +15,7 @@
</style>
<link rel="stylesheet" href="./css/print.css" type="text/css" media="print" />
<link rel="shortcut icon" href="/images/favicon.ico" />
- <meta name="Date-Revision-yyyymmdd" content="20130329" />
+ <meta name="Date-Revision-yyyymmdd" content="20130402" />
<meta http-equiv="Content-Language" content="en" />
<!--Google Analytics-->
<script type="text/javascript">
@@ -34,7 +34,7 @@
</head>
<body class="composite">
<div id="banner">
- <a href="./" id="bannerLeft">
+ <a href="../" id="bannerLeft">
<img src="images/hbase_logo.png" alt="Apache HBase" />
</a>
<!-- Commented out since we do not use it. St.Ack 20110906
@@ -86,6 +86,12 @@
<a href="https://reviews.apache.org" class="externalLink" title="ReviewBoard">ReviewBoard</a>
</li>
<li class="none">
+ <a href="builds.apache.org" title="Apache Build Box">Apache Build Box</a>
+ </li>
+ <li class="none">
+ <a href="http://54.241.6.143/" class="externalLink" title="EC2 Build Box">EC2 Build Box</a>
+ </li>
+ <li class="none">
<a href="team-list.html" title="Team">Team</a>
</li>
<li class="none">
@@ -719,8 +725,8 @@
<div id="footer">
<div class="xright">
- <span id="publishDate">Last Published: 2013-03-29</span>
- | <span id="projectVersion">Version: 0.97-SNAPSHOT</span>
+ <span id="publishDate">Last Published: 2013-04-02</span>
+ | <span id="projectVersion">Version: 0.97.0-SNAPSHOT</span>
</div>
<div class="xright">Copyright ©<a href="http://www.apache.org"> 2013
Modified: hbase/hbase.apache.org/trunk/resources.html
URL: http://svn.apache.org/viewvc/hbase/hbase.apache.org/trunk/resources.html?rev=1463652&r1=1463651&r2=1463652&view=diff
==============================================================================
--- hbase/hbase.apache.org/trunk/resources.html (original)
+++ hbase/hbase.apache.org/trunk/resources.html Tue Apr 2 18:06:19 2013
@@ -1,10 +1,10 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<!-- Generated by Apache Maven Doxia at Mar 29, 2013 -->
+<!-- Generated by Apache Maven Doxia at Apr 2, 2013 -->
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
- <title>HBase -
+ <title>HBase - Assembly -
Other Apache HBase (TM) Resources</title>
<style type="text/css" media="all">
@import url("./css/maven-base.css");
@@ -13,7 +13,7 @@
</style>
<link rel="stylesheet" href="./css/print.css" type="text/css" media="print" />
<link rel="shortcut icon" href="/images/favicon.ico" />
- <meta name="Date-Revision-yyyymmdd" content="20130329" />
+ <meta name="Date-Revision-yyyymmdd" content="20130402" />
<meta http-equiv="Content-Language" content="en" />
<!--Google Analytics-->
<script type="text/javascript">
@@ -32,7 +32,7 @@
</head>
<body class="composite">
<div id="banner">
- <a href="./" id="bannerLeft">
+ <a href="../" id="bannerLeft">
<img src="images/hbase_logo.png" alt="Apache HBase" />
</a>
<!-- Commented out since we do not use it. St.Ack 20110906
@@ -84,6 +84,12 @@
<a href="https://reviews.apache.org" class="externalLink" title="ReviewBoard">ReviewBoard</a>
</li>
<li class="none">
+ <a href="builds.apache.org" title="Apache Build Box">Apache Build Box</a>
+ </li>
+ <li class="none">
+ <a href="http://54.241.6.143/" class="externalLink" title="EC2 Build Box">EC2 Build Box</a>
+ </li>
+ <li class="none">
<a href="team-list.html" title="Team">Team</a>
</li>
<li class="none">
@@ -209,8 +215,8 @@
<div id="footer">
<div class="xright">
- <span id="publishDate">Last Published: 2013-03-29</span>
- | <span id="projectVersion">Version: 0.97-SNAPSHOT</span>
+ <span id="publishDate">Last Published: 2013-04-02</span>
+ | <span id="projectVersion">Version: 0.97.0-SNAPSHOT</span>
</div>
<div class="xright">Copyright ©<a href="http://www.apache.org"> 2013
Modified: hbase/hbase.apache.org/trunk/rpc.html
URL: http://svn.apache.org/viewvc/hbase/hbase.apache.org/trunk/rpc.html?rev=1463652&r1=1463651&r2=1463652&view=diff
==============================================================================
--- hbase/hbase.apache.org/trunk/rpc.html (original)
+++ hbase/hbase.apache.org/trunk/rpc.html Tue Apr 2 18:06:19 2013
@@ -1,16 +1,16 @@
<html><head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
- <title>Appendix A. 0.95 RPC Specification</title><link rel="stylesheet" type="text/css" href="css/freebsd_docbook.css"><meta name="generator" content="DocBook XSL-NS Stylesheets V1.76.1"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="appendix" title="Appendix A. 0.95 RPC Specification"><div class="titlepage"><div><div><h2 class="title"><a name="hbase.rpc"></a>Appendix A. 0.95 RPC Specification</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="#d551e22">A.1. Goals</a></span></dt><dt><span class="section"><a href="#d551e35">A.2. TODO</a></span></dt><dt><span class="section"><a href="#d551e51">A.3. RPC</a></span></dt><dd><dl><dt><span class="section"><a href="#d551e65">A.3.1. Connection Setup</a></span></dt><dt><span class="section"><a href="#d551e97">A.3.2. Request</a></span></dt><dt><span class="section"><a href="#d551e130">A.3.3. R
esponse</a></span></dt><dt><span class="section"><a href="#d551e160">A.3.4. Exceptions</a></span></dt><dt><span class="section"><a href="#d551e167">A.3.5. CellBlocks</a></span></dt></dl></dd><dt><span class="section"><a href="#d551e172">A.4. Notes</a></span></dt><dd><dl><dt><span class="section"><a href="#d551e175">A.4.1. Constraints</a></span></dt><dt><span class="section"><a href="#d551e180">A.4.2. One fat pb request or header+param</a></span></dt><dt><span class="section"><a href="#d551e200">A.4.3. Compression</a></span></dt></dl></dd></dl></div><p>In 0.95, all client/server communication is done with
+ <title>Appendix A. 0.95 RPC Specification</title><link rel="stylesheet" type="text/css" href="css/freebsd_docbook.css"><meta name="generator" content="DocBook XSL-NS Stylesheets V1.76.1"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="appendix" title="Appendix A. 0.95 RPC Specification"><div class="titlepage"><div><div><h2 class="title"><a name="hbase.rpc"></a>Appendix A. 0.95 RPC Specification</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="#d746e22">A.1. Goals</a></span></dt><dt><span class="section"><a href="#d746e35">A.2. TODO</a></span></dt><dt><span class="section"><a href="#d746e51">A.3. RPC</a></span></dt><dd><dl><dt><span class="section"><a href="#d746e65">A.3.1. Connection Setup</a></span></dt><dt><span class="section"><a href="#d746e97">A.3.2. Request</a></span></dt><dt><span class="section"><a href="#d746e130">A.3.3. R
esponse</a></span></dt><dt><span class="section"><a href="#d746e160">A.3.4. Exceptions</a></span></dt><dt><span class="section"><a href="#d746e167">A.3.5. CellBlocks</a></span></dt></dl></dd><dt><span class="section"><a href="#d746e172">A.4. Notes</a></span></dt><dd><dl><dt><span class="section"><a href="#d746e175">A.4.1. Constraints</a></span></dt><dt><span class="section"><a href="#d746e180">A.4.2. One fat pb request or header+param</a></span></dt><dt><span class="section"><a href="#d746e200">A.4.3. Compression</a></span></dt></dl></dd></dl></div><p>In 0.95, all client/server communication is done with
<a class="link" href="https://code.google.com/p/protobuf/" target="_top">protobuf’ed</a> Messages rather than with
<a class="link" href="http://hadoop.apache.org/docs/current/api/org/apache/hadoop/io/Writable.html" target="_top">Hadoop Writables</a>.
Our RPC wire format therefore changes.
This document describes the client/server request/response protocol and our new RPC wire-format.</p><p></p><p>For what RPC is like in 0.94 and previous,
see Benoît/Tsuna’s <a class="link" href="https://github.com/OpenTSDB/asynchbase/blob/master/src/HBaseRpc.java#L164" target="_top">Unofficial Hadoop / HBase RPC protocol documentation</a>.
For more background on how we arrived at this spec., see
- <a class="link" href="https://docs.google.com/document/d/1WCKwgaLDqBw2vpux0jPsAu2WPTRISob7HGCO8YhfDTA/edit#" target="_top">HBase RPC: WIP</a></p><p></p><div class="section" title="A.1. Goals"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="d551e22"></a>A.1. Goals</h2></div></div></div><p>
+ <a class="link" href="https://docs.google.com/document/d/1WCKwgaLDqBw2vpux0jPsAu2WPTRISob7HGCO8YhfDTA/edit#" target="_top">HBase RPC: WIP</a></p><p></p><div class="section" title="A.1. Goals"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="d746e22"></a>A.1. Goals</h2></div></div></div><p>
</p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><p>A wire-format we can evolve</p></li><li class="listitem"><p>A format that does not require our rewriting server core or
radically changing its current architecture (for later).</p></li></ol></div><p>
- </p></div><div class="section" title="A.2. TODO"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="d551e35"></a>A.2. TODO</h2></div></div></div><p>
+ </p></div><div class="section" title="A.2. TODO"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="d746e35"></a>A.2. TODO</h2></div></div></div><p>
</p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><p>List of problems with currently specified format and where
we would like to go in a version2, etc. For example, what would we
have to change if anything to move server async or to support
@@ -19,46 +19,46 @@
a grammar for the back and forth would help with groking rpc. Also,
a little state machine on client/server interactions would help
with understanding (and ensuring correct implementation).</p></li></ol></div><p>
- </p></div><div class="section" title="A.3. RPC"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="d551e51"></a>A.3. RPC</h2></div></div></div><p>The client will send setup information on connection establish.
+ </p></div><div class="section" title="A.3. RPC"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="d746e51"></a>A.3. RPC</h2></div></div></div><p>The client will send setup information on connection establish.
Thereafter, the client invokes methods against the remote server sending a protobuf Message and receiving a protobuf Message in response.
Communication is synchronous. All back and forth is preceded by an int that has the total length of the request/response.
Optionally, Cells(KeyValues) can be passed outside of protobufs in follow-behind Cell blocks (because
<a class="link" href="https://docs.google.com/document/d/1WEtrq-JTIUhlnlnvA0oYRLp0F8MKpEBeBSCFcQiacdw/edit#" target="_top">we can’t protobuf megabytes of KeyValues</a> or Cells).
These CellBlocks are encoded and optionally compressed.</p><p></p><p>For more detail on the protobufs involved, see the
- <a class="link" href="http://svn.apache.org/viewvc/hbase/trunk/hbase-protocol/src/main/protobuf/RPC.proto?view=markup" target="_top">RPC.proto</a> file in trunk.</p><div class="section" title="A.3.1. Connection Setup"><div class="titlepage"><div><div><h3 class="title"><a name="d551e65"></a>A.3.1. Connection Setup</h3></div></div></div><p>Client initiates connection.</p><div class="section" title="A.3.1.1. Client"><div class="titlepage"><div><div><h4 class="title"><a name="d551e70"></a>A.3.1.1. Client</h4></div></div></div><p>On connection setup, client sends a preamble followed by a connection header.
- </p><div class="section" title="A.3.1.1.1. <preamble>"><div class="titlepage"><div><div><h5 class="title"><a name="d551e75"></a>A.3.1.1.1. <preamble></h5></div></div></div><pre class="programlisting"><MAGIC 4 byte integer> <1 byte RPC Format Version> <1 byte auth type><sup>[<a name="d551e81" href="#ftn.d551e81" class="footnote">1</a>]</sup></pre><p>E.g.: HBas0x000x80 -- 4 bytes of MAGIC -- ‘HBas’ -- plus one-byte of version, 0 in this case, and one byte, 0x80 (SIMPLE). of an auth type.</p></div><div class="section" title="A.3.1.1.2. <Protobuf ConnectionHeader Message>"><div class="titlepage"><div><div><h5 class="title"><a name="d551e86"></a>A.3.1.1.2. <Protobuf ConnectionHeader Message></h5></div></div></div><p>Has user info, and “protocol”, as well as the encoders and compression the client will use sending CellBlocks.
+ <a class="link" href="http://svn.apache.org/viewvc/hbase/trunk/hbase-protocol/src/main/protobuf/RPC.proto?view=markup" target="_top">RPC.proto</a> file in trunk.</p><div class="section" title="A.3.1. Connection Setup"><div class="titlepage"><div><div><h3 class="title"><a name="d746e65"></a>A.3.1. Connection Setup</h3></div></div></div><p>Client initiates connection.</p><div class="section" title="A.3.1.1. Client"><div class="titlepage"><div><div><h4 class="title"><a name="d746e70"></a>A.3.1.1. Client</h4></div></div></div><p>On connection setup, client sends a preamble followed by a connection header.
+ </p><div class="section" title="A.3.1.1.1. <preamble>"><div class="titlepage"><div><div><h5 class="title"><a name="d746e75"></a>A.3.1.1.1. <preamble></h5></div></div></div><pre class="programlisting"><MAGIC 4 byte integer> <1 byte RPC Format Version> <1 byte auth type><sup>[<a name="d746e81" href="#ftn.d746e81" class="footnote">1</a>]</sup></pre><p>E.g.: HBas0x000x80 -- 4 bytes of MAGIC -- ‘HBas’ -- plus one-byte of version, 0 in this case, and one byte, 0x80 (SIMPLE). of an auth type.</p></div><div class="section" title="A.3.1.1.2. <Protobuf ConnectionHeader Message>"><div class="titlepage"><div><div><h5 class="title"><a name="d746e86"></a>A.3.1.1.2. <Protobuf ConnectionHeader Message></h5></div></div></div><p>Has user info, and “protocol”, as well as the encoders and compression the client will use sending CellBlocks.
CellBlock encoders and compressors are for the life of the connection.
CellBlock encoders implement org.apache.hadoop.hbase.codec.Codec.
CellBlocks may then also be compressed.
Compressors implement org.apache.hadoop.io.compress.CompressionCodec.
This protobuf is written using writeDelimited so is prefaced by a pb varint
- with its serialized length</p></div></div><div class="section" title="A.3.1.2. Server"><div class="titlepage"><div><div><h4 class="title"><a name="d551e92"></a>A.3.1.2. Server</h4></div></div></div><p>After client sends preamble and connection header,
+ with its serialized length</p></div></div><div class="section" title="A.3.1.2. Server"><div class="titlepage"><div><div><h4 class="title"><a name="d746e92"></a>A.3.1.2. Server</h4></div></div></div><p>After client sends preamble and connection header,
server does NOT respond if successful connection setup.
No response means server is READY to accept requests and to give out response.
If the version or authentication in the preamble is not agreeable or the server has trouble parsing the preamble,
it will throw a org.apache.hadoop.hbase.ipc.FatalConnectionException explaining the error and will then disconnect.
If the client in the connection header -- i.e. the protobuf’d Message that comes after the connection preamble -- asks for for a
- Service the server does not support or a codec the server does not have, again we throw a FatalConnectionException with explanation.</p></div></div><div class="section" title="A.3.2. Request"><div class="titlepage"><div><div><h3 class="title"><a name="d551e97"></a>A.3.2. Request</h3></div></div></div><p>After a Connection has been set up, client makes requests. Server responds.</p><p>A request is made up of a protobuf RequestHeader followed by a protobuf Message parameter.
+ Service the server does not support or a codec the server does not have, again we throw a FatalConnectionException with explanation.</p></div></div><div class="section" title="A.3.2. Request"><div class="titlepage"><div><div><h3 class="title"><a name="d746e97"></a>A.3.2. Request</h3></div></div></div><p>After a Connection has been set up, client makes requests. Server responds.</p><p>A request is made up of a protobuf RequestHeader followed by a protobuf Message parameter.
The header includes the method name and optionally, metadata on the optional CellBlock that may be following.
The parameter type suits the method being invoked: i.e. if we are doing a getRegionInfo request,
the protobuf Message param will be an instance of GetRegionInfoRequest.
The response will be a GetRegionInfoResponse.
- The CellBlock is optionally used ferrying the bulk of the RPC data: i.e Cells/KeyValues.</p><p></p><div class="section" title="A.3.2.1. Request Parts"><div class="titlepage"><div><div><h4 class="title"><a name="d551e105"></a>A.3.2.1. Request Parts</h4></div></div></div><div class="section" title="A.3.2.1.1. <Total Length>"><div class="titlepage"><div><div><h5 class="title"><a name="d551e108"></a>A.3.2.1.1. <Total Length></h5></div></div></div><p>The request is prefaced by an int that holds the total length of what follows.</p></div><div class="section" title="A.3.2.1.2. <Protobuf RequestHeader Message>"><div class="titlepage"><div><div><h5 class="title"><a name="d551e113"></a>A.3.2.1.2. <Protobuf RequestHeader Message></h5></div></div></div><p>Will have call.id, trace.id, and method name, etc. including optional Metadata on the Cell block IFF one is following.
- Data is protobuf’d inline in this pb Message or optionally comes in the following CellBlock</p></div><div class="section" title="A.3.2.1.3. <Protobuf Param Message>"><div class="titlepage"><div><div><h5 class="title"><a name="d551e118"></a>A.3.2.1.3. <Protobuf Param Message></h5></div></div></div><p>If the method being invoked is getRegionInfo, if you study the Service descriptor for the client to regionserver protocol,
- you will find that the request sends a GetRegionInfoRequest protobuf Message param in this position.</p></div><div class="section" title="A.3.2.1.4. <CellBlock>"><div class="titlepage"><div><div><h5 class="title"><a name="d551e123"></a>A.3.2.1.4. <CellBlock></h5></div></div></div><p>An encoded and optionally compressed Cell block.</p></div></div></div><div class="section" title="A.3.3. Response"><div class="titlepage"><div><div><h3 class="title"><a name="d551e130"></a>A.3.3. Response</h3></div></div></div><p>Same as Request, it is a protobuf ResponseHeader followed by a protobuf Message response where the Message response type suits the method invoked.
- Bulk of the data may come in a following CellBlock.</p><div class="section" title="A.3.3.1. Response Parts"><div class="titlepage"><div><div><h4 class="title"><a name="d551e135"></a>A.3.3.1. Response Parts</h4></div></div></div><div class="section" title="A.3.3.1.1. <Total Length>"><div class="titlepage"><div><div><h5 class="title"><a name="d551e138"></a>A.3.3.1.1. <Total Length></h5></div></div></div><p>The response is prefaced by an int that holds the total length of what follows.</p></div><div class="section" title="A.3.3.1.2. <Protobuf ResponseHeader Message>"><div class="titlepage"><div><div><h5 class="title"><a name="d551e143"></a>A.3.3.1.2. <Protobuf ResponseHeader Message></h5></div></div></div><p>Will have call.id, etc. Will include exception if failed processing. Optionally includes metadata on optional, IFF there is a CellBlock following.</p></div><div class="section" title="A.3.3.1.3. <Protobuf
Response Message>"><div class="titlepage"><div><div><h5 class="title"><a name="d551e148"></a>A.3.3.1.3. <Protobuf Response Message></h5></div></div></div><p>Return or may be nothing if exception. If the method being invoked is getRegionInfo, if you study the Service descriptor for the client to regionserver protocol,
- you will find that the response sends a GetRegionInfoResponse protobuf Message param in this position.</p></div><div class="section" title="A.3.3.1.4. <CellBlock>"><div class="titlepage"><div><div><h5 class="title"><a name="d551e153"></a>A.3.3.1.4. <CellBlock></h5></div></div></div><p>An encoded and optionally compressed Cell block.</p></div></div></div><div class="section" title="A.3.4. Exceptions"><div class="titlepage"><div><div><h3 class="title"><a name="d551e160"></a>A.3.4. Exceptions</h3></div></div></div><p>There are two distinct types.
+ The CellBlock is optionally used ferrying the bulk of the RPC data: i.e Cells/KeyValues.</p><p></p><div class="section" title="A.3.2.1. Request Parts"><div class="titlepage"><div><div><h4 class="title"><a name="d746e105"></a>A.3.2.1. Request Parts</h4></div></div></div><div class="section" title="A.3.2.1.1. <Total Length>"><div class="titlepage"><div><div><h5 class="title"><a name="d746e108"></a>A.3.2.1.1. <Total Length></h5></div></div></div><p>The request is prefaced by an int that holds the total length of what follows.</p></div><div class="section" title="A.3.2.1.2. <Protobuf RequestHeader Message>"><div class="titlepage"><div><div><h5 class="title"><a name="d746e113"></a>A.3.2.1.2. <Protobuf RequestHeader Message></h5></div></div></div><p>Will have call.id, trace.id, and method name, etc. including optional Metadata on the Cell block IFF one is following.
+ Data is protobuf’d inline in this pb Message or optionally comes in the following CellBlock</p></div><div class="section" title="A.3.2.1.3. <Protobuf Param Message>"><div class="titlepage"><div><div><h5 class="title"><a name="d746e118"></a>A.3.2.1.3. <Protobuf Param Message></h5></div></div></div><p>If the method being invoked is getRegionInfo, if you study the Service descriptor for the client to regionserver protocol,
+ you will find that the request sends a GetRegionInfoRequest protobuf Message param in this position.</p></div><div class="section" title="A.3.2.1.4. <CellBlock>"><div class="titlepage"><div><div><h5 class="title"><a name="d746e123"></a>A.3.2.1.4. <CellBlock></h5></div></div></div><p>An encoded and optionally compressed Cell block.</p></div></div></div><div class="section" title="A.3.3. Response"><div class="titlepage"><div><div><h3 class="title"><a name="d746e130"></a>A.3.3. Response</h3></div></div></div><p>Same as Request, it is a protobuf ResponseHeader followed by a protobuf Message response where the Message response type suits the method invoked.
+ Bulk of the data may come in a following CellBlock.</p><div class="section" title="A.3.3.1. Response Parts"><div class="titlepage"><div><div><h4 class="title"><a name="d746e135"></a>A.3.3.1. Response Parts</h4></div></div></div><div class="section" title="A.3.3.1.1. <Total Length>"><div class="titlepage"><div><div><h5 class="title"><a name="d746e138"></a>A.3.3.1.1. <Total Length></h5></div></div></div><p>The response is prefaced by an int that holds the total length of what follows.</p></div><div class="section" title="A.3.3.1.2. <Protobuf ResponseHeader Message>"><div class="titlepage"><div><div><h5 class="title"><a name="d746e143"></a>A.3.3.1.2. <Protobuf ResponseHeader Message></h5></div></div></div><p>Will have call.id, etc. Will include exception if failed processing. Optionally includes metadata on optional, IFF there is a CellBlock following.</p></div><div class="section" title="A.3.3.1.3. <Protobuf
Response Message>"><div class="titlepage"><div><div><h5 class="title"><a name="d746e148"></a>A.3.3.1.3. <Protobuf Response Message></h5></div></div></div><p>Return or may be nothing if exception. If the method being invoked is getRegionInfo, if you study the Service descriptor for the client to regionserver protocol,
+ you will find that the response sends a GetRegionInfoResponse protobuf Message param in this position.</p></div><div class="section" title="A.3.3.1.4. <CellBlock>"><div class="titlepage"><div><div><h5 class="title"><a name="d746e153"></a>A.3.3.1.4. <CellBlock></h5></div></div></div><p>An encoded and optionally compressed Cell block.</p></div></div></div><div class="section" title="A.3.4. Exceptions"><div class="titlepage"><div><div><h3 class="title"><a name="d746e160"></a>A.3.4. Exceptions</h3></div></div></div><p>There are two distinct types.
There is the request failed which is encapsulated inside the response header for the response.
The connection stays open to receive new requests.
The second type, the FatalConnectionException, kills the connection.</p><p>Exceptions can carry extra information.
See the ExceptionResponse protobuf type.
- It has a flag to indicate do-no-retry as well as other miscellaneous payload to help improve client responsiveness.</p></div><div class="section" title="A.3.5. CellBlocks"><div class="titlepage"><div><div><h3 class="title"><a name="d551e167"></a>A.3.5. CellBlocks</h3></div></div></div><p>These are not versioned.
+ It has a flag to indicate do-no-retry as well as other miscellaneous payload to help improve client responsiveness.</p></div><div class="section" title="A.3.5. CellBlocks"><div class="titlepage"><div><div><h3 class="title"><a name="d746e167"></a>A.3.5. CellBlocks</h3></div></div></div><p>These are not versioned.
Server can do the codec or it cannot.
If new version of a codec with say, tighter encoding, then give it a new class name.
- Codecs will live on the server for all time so old clients can connect.</p></div></div><div class="section" title="A.4. Notes"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="d551e172"></a>A.4. Notes</h2></div></div></div><div class="section" title="A.4.1. Constraints"><div class="titlepage"><div><div><h3 class="title"><a name="d551e175"></a>A.4.1. Constraints</h3></div></div></div><p>In some part, current wire-format -- i.e. all requests and responses preceeded by a length -- has been dictated by current server non-async architecture.</p></div><div class="section" title="A.4.2. One fat pb request or header+param"><div class="titlepage"><div><div><h3 class="title"><a name="d551e180"></a>A.4.2. One fat pb request or header+param</h3></div></div></div><p>We went with pb header followed by pb param making a request and a pb header followed by pb response for now.
+ Codecs will live on the server for all time so old clients can connect.</p></div></div><div class="section" title="A.4. Notes"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="d746e172"></a>A.4. Notes</h2></div></div></div><div class="section" title="A.4.1. Constraints"><div class="titlepage"><div><div><h3 class="title"><a name="d746e175"></a>A.4.1. Constraints</h3></div></div></div><p>In some part, current wire-format -- i.e. all requests and responses preceeded by a length -- has been dictated by current server non-async architecture.</p></div><div class="section" title="A.4.2. One fat pb request or header+param"><div class="titlepage"><div><div><h3 class="title"><a name="d746e180"></a>A.4.2. One fat pb request or header+param</h3></div></div></div><p>We went with pb header followed by pb param making a request and a pb header followed by pb response for now.
Doing header+param rather than a single protobuf Message with both header and param content:</p><p>
</p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><p>Is closer to what we currently have</p></li><li class="listitem"><p>Having a single fat pb requires extra copying putting the already pb’d param into the body of the fat request pb (and same making result)</p></li><li class="listitem"><p>We can decide whether to accept the request or not before we read the param; for example, the request might be low priority. As is, we read header+param in one go as server is currently implemented so this is a TODO.</p></li></ol></div><p>
- </p><p>The advantages are minor. If later, fat request has clear advantage, can roll out a v2 later.</p></div><div class="section" title="A.4.3. Compression"><div class="titlepage"><div><div><h3 class="title"><a name="d551e200"></a>A.4.3. Compression</h3></div></div></div><p>Uses hadoops compression codecs.</p></div></div><div class="footnotes"><br><hr width="100" align="left"><div class="footnote"><p><sup>[<a id="ftn.d551e81" href="#d551e81" class="para">1</a>] </sup> We need the auth method spec. here so the connection header is encoded if auth enabled.</p></div></div></div><div id="disqus_thread"></div><script type="text/javascript">
+ </p><p>The advantages are minor. If later, fat request has clear advantage, can roll out a v2 later.</p></div><div class="section" title="A.4.3. Compression"><div class="titlepage"><div><div><h3 class="title"><a name="d746e200"></a>A.4.3. Compression</h3></div></div></div><p>Uses hadoops compression codecs.</p></div></div><div class="footnotes"><br><hr width="100" align="left"><div class="footnote"><p><sup>[<a id="ftn.d746e81" href="#d746e81" class="para">1</a>] </sup> We need the auth method spec. here so the connection header is encoded if auth enabled.</p></div></div></div><div id="disqus_thread"></div><script type="text/javascript">
var disqus_shortname = 'hbase'; // required: replace example with your forum shortname
var disqus_url = 'http://hbase.apache.org/book';
var disqus_identifier = 'hbase.rpc';
Modified: hbase/hbase.apache.org/trunk/rpc/apas02.html
URL: http://svn.apache.org/viewvc/hbase/hbase.apache.org/trunk/rpc/apas02.html?rev=1463652&r1=1463651&r2=1463652&view=diff
==============================================================================
--- hbase/hbase.apache.org/trunk/rpc/apas02.html (original)
+++ hbase/hbase.apache.org/trunk/rpc/apas02.html Tue Apr 2 18:06:19 2013
@@ -1,6 +1,6 @@
<html><head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
- <title>A.2. TODO</title><link rel="stylesheet" type="text/css" href="../css/freebsd_docbook.css"><meta name="generator" content="DocBook XSL-NS Stylesheets V1.76.1"><link rel="home" href="rpc.html" title="Appendix A. 0.95 RPC Specification"><link rel="up" href="rpc.html" title="Appendix A. 0.95 RPC Specification"><link rel="prev" href="rpc.html" title="Appendix A. 0.95 RPC Specification"><link rel="next" href="apas03.html" title="A.3. RPC"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">A.2. TODO</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="rpc.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="apas03.html">Next</a></td></tr></table><hr></div><div class="section" title="A.2. TODO"><div
class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="d551e35"></a>A.2. TODO</h2></div></div></div><p>
+ <title>A.2. TODO</title><link rel="stylesheet" type="text/css" href="../css/freebsd_docbook.css"><meta name="generator" content="DocBook XSL-NS Stylesheets V1.76.1"><link rel="home" href="rpc.html" title="Appendix A. 0.95 RPC Specification"><link rel="up" href="rpc.html" title="Appendix A. 0.95 RPC Specification"><link rel="prev" href="rpc.html" title="Appendix A. 0.95 RPC Specification"><link rel="next" href="apas03.html" title="A.3. RPC"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">A.2. TODO</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="rpc.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="apas03.html">Next</a></td></tr></table><hr></div><div class="section" title="A.2. TODO"><div
class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="d746e35"></a>A.2. TODO</h2></div></div></div><p>
</p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><p>List of problems with currently specified format and where
we would like to go in a version2, etc. For example, what would we
have to change if anything to move server async or to support
Modified: hbase/hbase.apache.org/trunk/rpc/apas03.html
URL: http://svn.apache.org/viewvc/hbase/hbase.apache.org/trunk/rpc/apas03.html?rev=1463652&r1=1463651&r2=1463652&view=diff
==============================================================================
--- hbase/hbase.apache.org/trunk/rpc/apas03.html (original)
+++ hbase/hbase.apache.org/trunk/rpc/apas03.html Tue Apr 2 18:06:19 2013
@@ -1,42 +1,42 @@
<html><head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
- <title>A.3. RPC</title><link rel="stylesheet" type="text/css" href="../css/freebsd_docbook.css"><meta name="generator" content="DocBook XSL-NS Stylesheets V1.76.1"><link rel="home" href="rpc.html" title="Appendix A. 0.95 RPC Specification"><link rel="up" href="rpc.html" title="Appendix A. 0.95 RPC Specification"><link rel="prev" href="apas02.html" title="A.2. TODO"><link rel="next" href="apas04.html" title="A.4. Notes"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">A.3. RPC</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="apas02.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="apas04.html">Next</a></td></tr></table><hr></div><div class="section" title="A.3. RPC"><div class="titlepage"><div><
div><h2 class="title" style="clear: both"><a name="d551e51"></a>A.3. RPC</h2></div></div></div><p>The client will send setup information on connection establish.
+ <title>A.3. RPC</title><link rel="stylesheet" type="text/css" href="../css/freebsd_docbook.css"><meta name="generator" content="DocBook XSL-NS Stylesheets V1.76.1"><link rel="home" href="rpc.html" title="Appendix A. 0.95 RPC Specification"><link rel="up" href="rpc.html" title="Appendix A. 0.95 RPC Specification"><link rel="prev" href="apas02.html" title="A.2. TODO"><link rel="next" href="apas04.html" title="A.4. Notes"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">A.3. RPC</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="apas02.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="apas04.html">Next</a></td></tr></table><hr></div><div class="section" title="A.3. RPC"><div class="titlepage"><div><
div><h2 class="title" style="clear: both"><a name="d746e51"></a>A.3. RPC</h2></div></div></div><p>The client will send setup information on connection establish.
Thereafter, the client invokes methods against the remote server sending a protobuf Message and receiving a protobuf Message in response.
Communication is synchronous. All back and forth is preceded by an int that has the total length of the request/response.
Optionally, Cells(KeyValues) can be passed outside of protobufs in follow-behind Cell blocks (because
<a class="link" href="https://docs.google.com/document/d/1WEtrq-JTIUhlnlnvA0oYRLp0F8MKpEBeBSCFcQiacdw/edit#" target="_top">we can’t protobuf megabytes of KeyValues</a> or Cells).
These CellBlocks are encoded and optionally compressed.</p><p></p><p>For more detail on the protobufs involved, see the
- <a class="link" href="http://svn.apache.org/viewvc/hbase/trunk/hbase-protocol/src/main/protobuf/RPC.proto?view=markup" target="_top">RPC.proto</a> file in trunk.</p><div class="section" title="A.3.1. Connection Setup"><div class="titlepage"><div><div><h3 class="title"><a name="d551e65"></a>A.3.1. Connection Setup</h3></div></div></div><p>Client initiates connection.</p><div class="section" title="A.3.1.1. Client"><div class="titlepage"><div><div><h4 class="title"><a name="d551e70"></a>A.3.1.1. Client</h4></div></div></div><p>On connection setup, client sends a preamble followed by a connection header.
- </p><div class="section" title="A.3.1.1.1. <preamble>"><div class="titlepage"><div><div><h5 class="title"><a name="d551e75"></a>A.3.1.1.1. <preamble></h5></div></div></div><pre class="programlisting"><MAGIC 4 byte integer> <1 byte RPC Format Version> <1 byte auth type><sup>[<a name="d551e81" href="#ftn.d551e81" class="footnote">1</a>]</sup></pre><p>E.g.: HBas0x000x80 -- 4 bytes of MAGIC -- ‘HBas’ -- plus one-byte of version, 0 in this case, and one byte, 0x80 (SIMPLE). of an auth type.</p></div><div class="section" title="A.3.1.1.2. <Protobuf ConnectionHeader Message>"><div class="titlepage"><div><div><h5 class="title"><a name="d551e86"></a>A.3.1.1.2. <Protobuf ConnectionHeader Message></h5></div></div></div><p>Has user info, and “protocol”, as well as the encoders and compression the client will use sending CellBlocks.
+ <a class="link" href="http://svn.apache.org/viewvc/hbase/trunk/hbase-protocol/src/main/protobuf/RPC.proto?view=markup" target="_top">RPC.proto</a> file in trunk.</p><div class="section" title="A.3.1. Connection Setup"><div class="titlepage"><div><div><h3 class="title"><a name="d746e65"></a>A.3.1. Connection Setup</h3></div></div></div><p>Client initiates connection.</p><div class="section" title="A.3.1.1. Client"><div class="titlepage"><div><div><h4 class="title"><a name="d746e70"></a>A.3.1.1. Client</h4></div></div></div><p>On connection setup, client sends a preamble followed by a connection header.
+ </p><div class="section" title="A.3.1.1.1. <preamble>"><div class="titlepage"><div><div><h5 class="title"><a name="d746e75"></a>A.3.1.1.1. <preamble></h5></div></div></div><pre class="programlisting"><MAGIC 4 byte integer> <1 byte RPC Format Version> <1 byte auth type><sup>[<a name="d746e81" href="#ftn.d746e81" class="footnote">1</a>]</sup></pre><p>E.g.: HBas0x000x80 -- 4 bytes of MAGIC -- ‘HBas’ -- plus one-byte of version, 0 in this case, and one byte, 0x80 (SIMPLE). of an auth type.</p></div><div class="section" title="A.3.1.1.2. <Protobuf ConnectionHeader Message>"><div class="titlepage"><div><div><h5 class="title"><a name="d746e86"></a>A.3.1.1.2. <Protobuf ConnectionHeader Message></h5></div></div></div><p>Has user info, and “protocol”, as well as the encoders and compression the client will use sending CellBlocks.
CellBlock encoders and compressors are for the life of the connection.
CellBlock encoders implement org.apache.hadoop.hbase.codec.Codec.
CellBlocks may then also be compressed.
Compressors implement org.apache.hadoop.io.compress.CompressionCodec.
This protobuf is written using writeDelimited so is prefaced by a pb varint
- with its serialized length</p></div></div><div class="section" title="A.3.1.2. Server"><div class="titlepage"><div><div><h4 class="title"><a name="d551e92"></a>A.3.1.2. Server</h4></div></div></div><p>After client sends preamble and connection header,
+ with its serialized length</p></div></div><div class="section" title="A.3.1.2. Server"><div class="titlepage"><div><div><h4 class="title"><a name="d746e92"></a>A.3.1.2. Server</h4></div></div></div><p>After client sends preamble and connection header,
server does NOT respond if successful connection setup.
No response means server is READY to accept requests and to give out response.
If the version or authentication in the preamble is not agreeable or the server has trouble parsing the preamble,
it will throw a org.apache.hadoop.hbase.ipc.FatalConnectionException explaining the error and will then disconnect.
If the client in the connection header -- i.e. the protobuf’d Message that comes after the connection preamble -- asks for for a
- Service the server does not support or a codec the server does not have, again we throw a FatalConnectionException with explanation.</p></div></div><div class="section" title="A.3.2. Request"><div class="titlepage"><div><div><h3 class="title"><a name="d551e97"></a>A.3.2. Request</h3></div></div></div><p>After a Connection has been set up, client makes requests. Server responds.</p><p>A request is made up of a protobuf RequestHeader followed by a protobuf Message parameter.
+ Service the server does not support or a codec the server does not have, again we throw a FatalConnectionException with explanation.</p></div></div><div class="section" title="A.3.2. Request"><div class="titlepage"><div><div><h3 class="title"><a name="d746e97"></a>A.3.2. Request</h3></div></div></div><p>After a Connection has been set up, client makes requests. Server responds.</p><p>A request is made up of a protobuf RequestHeader followed by a protobuf Message parameter.
The header includes the method name and optionally, metadata on the optional CellBlock that may be following.
The parameter type suits the method being invoked: i.e. if we are doing a getRegionInfo request,
the protobuf Message param will be an instance of GetRegionInfoRequest.
The response will be a GetRegionInfoResponse.
- The CellBlock is optionally used ferrying the bulk of the RPC data: i.e Cells/KeyValues.</p><p></p><div class="section" title="A.3.2.1. Request Parts"><div class="titlepage"><div><div><h4 class="title"><a name="d551e105"></a>A.3.2.1. Request Parts</h4></div></div></div><div class="section" title="A.3.2.1.1. <Total Length>"><div class="titlepage"><div><div><h5 class="title"><a name="d551e108"></a>A.3.2.1.1. <Total Length></h5></div></div></div><p>The request is prefaced by an int that holds the total length of what follows.</p></div><div class="section" title="A.3.2.1.2. <Protobuf RequestHeader Message>"><div class="titlepage"><div><div><h5 class="title"><a name="d551e113"></a>A.3.2.1.2. <Protobuf RequestHeader Message></h5></div></div></div><p>Will have call.id, trace.id, and method name, etc. including optional Metadata on the Cell block IFF one is following.
- Data is protobuf’d inline in this pb Message or optionally comes in the following CellBlock</p></div><div class="section" title="A.3.2.1.3. <Protobuf Param Message>"><div class="titlepage"><div><div><h5 class="title"><a name="d551e118"></a>A.3.2.1.3. <Protobuf Param Message></h5></div></div></div><p>If the method being invoked is getRegionInfo, if you study the Service descriptor for the client to regionserver protocol,
- you will find that the request sends a GetRegionInfoRequest protobuf Message param in this position.</p></div><div class="section" title="A.3.2.1.4. <CellBlock>"><div class="titlepage"><div><div><h5 class="title"><a name="d551e123"></a>A.3.2.1.4. <CellBlock></h5></div></div></div><p>An encoded and optionally compressed Cell block.</p></div></div></div><div class="section" title="A.3.3. Response"><div class="titlepage"><div><div><h3 class="title"><a name="d551e130"></a>A.3.3. Response</h3></div></div></div><p>Same as Request, it is a protobuf ResponseHeader followed by a protobuf Message response where the Message response type suits the method invoked.
- Bulk of the data may come in a following CellBlock.</p><div class="section" title="A.3.3.1. Response Parts"><div class="titlepage"><div><div><h4 class="title"><a name="d551e135"></a>A.3.3.1. Response Parts</h4></div></div></div><div class="section" title="A.3.3.1.1. <Total Length>"><div class="titlepage"><div><div><h5 class="title"><a name="d551e138"></a>A.3.3.1.1. <Total Length></h5></div></div></div><p>The response is prefaced by an int that holds the total length of what follows.</p></div><div class="section" title="A.3.3.1.2. <Protobuf ResponseHeader Message>"><div class="titlepage"><div><div><h5 class="title"><a name="d551e143"></a>A.3.3.1.2. <Protobuf ResponseHeader Message></h5></div></div></div><p>Will have call.id, etc. Will include exception if failed processing. Optionally includes metadata on optional, IFF there is a CellBlock following.</p></div><div class="section" title="A.3.3.1.3. <Protobuf
Response Message>"><div class="titlepage"><div><div><h5 class="title"><a name="d551e148"></a>A.3.3.1.3. <Protobuf Response Message></h5></div></div></div><p>Return or may be nothing if exception. If the method being invoked is getRegionInfo, if you study the Service descriptor for the client to regionserver protocol,
- you will find that the response sends a GetRegionInfoResponse protobuf Message param in this position.</p></div><div class="section" title="A.3.3.1.4. <CellBlock>"><div class="titlepage"><div><div><h5 class="title"><a name="d551e153"></a>A.3.3.1.4. <CellBlock></h5></div></div></div><p>An encoded and optionally compressed Cell block.</p></div></div></div><div class="section" title="A.3.4. Exceptions"><div class="titlepage"><div><div><h3 class="title"><a name="d551e160"></a>A.3.4. Exceptions</h3></div></div></div><p>There are two distinct types.
+ The CellBlock is optionally used ferrying the bulk of the RPC data: i.e Cells/KeyValues.</p><p></p><div class="section" title="A.3.2.1. Request Parts"><div class="titlepage"><div><div><h4 class="title"><a name="d746e105"></a>A.3.2.1. Request Parts</h4></div></div></div><div class="section" title="A.3.2.1.1. <Total Length>"><div class="titlepage"><div><div><h5 class="title"><a name="d746e108"></a>A.3.2.1.1. <Total Length></h5></div></div></div><p>The request is prefaced by an int that holds the total length of what follows.</p></div><div class="section" title="A.3.2.1.2. <Protobuf RequestHeader Message>"><div class="titlepage"><div><div><h5 class="title"><a name="d746e113"></a>A.3.2.1.2. <Protobuf RequestHeader Message></h5></div></div></div><p>Will have call.id, trace.id, and method name, etc. including optional Metadata on the Cell block IFF one is following.
+ Data is protobuf’d inline in this pb Message or optionally comes in the following CellBlock</p></div><div class="section" title="A.3.2.1.3. <Protobuf Param Message>"><div class="titlepage"><div><div><h5 class="title"><a name="d746e118"></a>A.3.2.1.3. <Protobuf Param Message></h5></div></div></div><p>If the method being invoked is getRegionInfo, if you study the Service descriptor for the client to regionserver protocol,
+ you will find that the request sends a GetRegionInfoRequest protobuf Message param in this position.</p></div><div class="section" title="A.3.2.1.4. <CellBlock>"><div class="titlepage"><div><div><h5 class="title"><a name="d746e123"></a>A.3.2.1.4. <CellBlock></h5></div></div></div><p>An encoded and optionally compressed Cell block.</p></div></div></div><div class="section" title="A.3.3. Response"><div class="titlepage"><div><div><h3 class="title"><a name="d746e130"></a>A.3.3. Response</h3></div></div></div><p>Same as Request, it is a protobuf ResponseHeader followed by a protobuf Message response where the Message response type suits the method invoked.
+ Bulk of the data may come in a following CellBlock.</p><div class="section" title="A.3.3.1. Response Parts"><div class="titlepage"><div><div><h4 class="title"><a name="d746e135"></a>A.3.3.1. Response Parts</h4></div></div></div><div class="section" title="A.3.3.1.1. <Total Length>"><div class="titlepage"><div><div><h5 class="title"><a name="d746e138"></a>A.3.3.1.1. <Total Length></h5></div></div></div><p>The response is prefaced by an int that holds the total length of what follows.</p></div><div class="section" title="A.3.3.1.2. <Protobuf ResponseHeader Message>"><div class="titlepage"><div><div><h5 class="title"><a name="d746e143"></a>A.3.3.1.2. <Protobuf ResponseHeader Message></h5></div></div></div><p>Will have call.id, etc. Will include exception if failed processing. Optionally includes metadata on optional, IFF there is a CellBlock following.</p></div><div class="section" title="A.3.3.1.3. <Protobuf
Response Message>"><div class="titlepage"><div><div><h5 class="title"><a name="d746e148"></a>A.3.3.1.3. <Protobuf Response Message></h5></div></div></div><p>Return or may be nothing if exception. If the method being invoked is getRegionInfo, if you study the Service descriptor for the client to regionserver protocol,
+ you will find that the response sends a GetRegionInfoResponse protobuf Message param in this position.</p></div><div class="section" title="A.3.3.1.4. <CellBlock>"><div class="titlepage"><div><div><h5 class="title"><a name="d746e153"></a>A.3.3.1.4. <CellBlock></h5></div></div></div><p>An encoded and optionally compressed Cell block.</p></div></div></div><div class="section" title="A.3.4. Exceptions"><div class="titlepage"><div><div><h3 class="title"><a name="d746e160"></a>A.3.4. Exceptions</h3></div></div></div><p>There are two distinct types.
There is the request failed which is encapsulated inside the response header for the response.
The connection stays open to receive new requests.
The second type, the FatalConnectionException, kills the connection.</p><p>Exceptions can carry extra information.
See the ExceptionResponse protobuf type.
- It has a flag to indicate do-no-retry as well as other miscellaneous payload to help improve client responsiveness.</p></div><div class="section" title="A.3.5. CellBlocks"><div class="titlepage"><div><div><h3 class="title"><a name="d551e167"></a>A.3.5. CellBlocks</h3></div></div></div><p>These are not versioned.
+ It has a flag to indicate do-no-retry as well as other miscellaneous payload to help improve client responsiveness.</p></div><div class="section" title="A.3.5. CellBlocks"><div class="titlepage"><div><div><h3 class="title"><a name="d746e167"></a>A.3.5. CellBlocks</h3></div></div></div><p>These are not versioned.
Server can do the codec or it cannot.
If new version of a codec with say, tighter encoding, then give it a new class name.
- Codecs will live on the server for all time so old clients can connect.</p></div><div class="footnotes"><br><hr width="100" align="left"><div class="footnote"><p><sup>[<a id="ftn.d551e81" href="#d551e81" class="para">1</a>] </sup> We need the auth method spec. here so the connection header is encoded if auth enabled.</p></div></div></div><div id="disqus_thread"></div><script type="text/javascript">
+ Codecs will live on the server for all time so old clients can connect.</p></div><div class="footnotes"><br><hr width="100" align="left"><div class="footnote"><p><sup>[<a id="ftn.d746e81" href="#d746e81" class="para">1</a>] </sup> We need the auth method spec. here so the connection header is encoded if auth enabled.</p></div></div></div><div id="disqus_thread"></div><script type="text/javascript">
var disqus_shortname = 'hbase'; // required: replace example with your forum shortname
var disqus_url = 'http://hbase.apache.org/book';
var disqus_identifier = '';
Modified: hbase/hbase.apache.org/trunk/rpc/apas04.html
URL: http://svn.apache.org/viewvc/hbase/hbase.apache.org/trunk/rpc/apas04.html?rev=1463652&r1=1463651&r2=1463652&view=diff
==============================================================================
--- hbase/hbase.apache.org/trunk/rpc/apas04.html (original)
+++ hbase/hbase.apache.org/trunk/rpc/apas04.html Tue Apr 2 18:06:19 2013
@@ -1,9 +1,9 @@
<html><head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
- <title>A.4. Notes</title><link rel="stylesheet" type="text/css" href="../css/freebsd_docbook.css"><meta name="generator" content="DocBook XSL-NS Stylesheets V1.76.1"><link rel="home" href="rpc.html" title="Appendix A. 0.95 RPC Specification"><link rel="up" href="rpc.html" title="Appendix A. 0.95 RPC Specification"><link rel="prev" href="apas03.html" title="A.3. RPC"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">A.4. Notes</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="apas03.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> </td></tr></table><hr></div><div class="section" title="A.4. Notes"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="d551e172"></a>A.4. Notes</h2></div></div></
div><div class="section" title="A.4.1. Constraints"><div class="titlepage"><div><div><h3 class="title"><a name="d551e175"></a>A.4.1. Constraints</h3></div></div></div><p>In some part, current wire-format -- i.e. all requests and responses preceeded by a length -- has been dictated by current server non-async architecture.</p></div><div class="section" title="A.4.2. One fat pb request or header+param"><div class="titlepage"><div><div><h3 class="title"><a name="d551e180"></a>A.4.2. One fat pb request or header+param</h3></div></div></div><p>We went with pb header followed by pb param making a request and a pb header followed by pb response for now.
+ <title>A.4. Notes</title><link rel="stylesheet" type="text/css" href="../css/freebsd_docbook.css"><meta name="generator" content="DocBook XSL-NS Stylesheets V1.76.1"><link rel="home" href="rpc.html" title="Appendix A. 0.95 RPC Specification"><link rel="up" href="rpc.html" title="Appendix A. 0.95 RPC Specification"><link rel="prev" href="apas03.html" title="A.3. RPC"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">A.4. Notes</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="apas03.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> </td></tr></table><hr></div><div class="section" title="A.4. Notes"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="d746e172"></a>A.4. Notes</h2></div></div></
div><div class="section" title="A.4.1. Constraints"><div class="titlepage"><div><div><h3 class="title"><a name="d746e175"></a>A.4.1. Constraints</h3></div></div></div><p>In some part, current wire-format -- i.e. all requests and responses preceeded by a length -- has been dictated by current server non-async architecture.</p></div><div class="section" title="A.4.2. One fat pb request or header+param"><div class="titlepage"><div><div><h3 class="title"><a name="d746e180"></a>A.4.2. One fat pb request or header+param</h3></div></div></div><p>We went with pb header followed by pb param making a request and a pb header followed by pb response for now.
Doing header+param rather than a single protobuf Message with both header and param content:</p><p>
</p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><p>Is closer to what we currently have</p></li><li class="listitem"><p>Having a single fat pb requires extra copying putting the already pb’d param into the body of the fat request pb (and same making result)</p></li><li class="listitem"><p>We can decide whether to accept the request or not before we read the param; for example, the request might be low priority. As is, we read header+param in one go as server is currently implemented so this is a TODO.</p></li></ol></div><p>
- </p><p>The advantages are minor. If later, fat request has clear advantage, can roll out a v2 later.</p></div><div class="section" title="A.4.3. Compression"><div class="titlepage"><div><div><h3 class="title"><a name="d551e200"></a>A.4.3. Compression</h3></div></div></div><p>Uses hadoops compression codecs.</p></div></div><div id="disqus_thread"></div><script type="text/javascript">
+ </p><p>The advantages are minor. If later, fat request has clear advantage, can roll out a v2 later.</p></div><div class="section" title="A.4.3. Compression"><div class="titlepage"><div><div><h3 class="title"><a name="d746e200"></a>A.4.3. Compression</h3></div></div></div><p>Uses hadoops compression codecs.</p></div></div><div id="disqus_thread"></div><script type="text/javascript">
var disqus_shortname = 'hbase'; // required: replace example with your forum shortname
var disqus_url = 'http://hbase.apache.org/book';
var disqus_identifier = '';