http://git-wip-us.apache.org/repos/asf/hbase-site/blob/b707139a/book.html ---------------------------------------------------------------------- diff --git a/book.html b/book.html index 7854e62..cbbdddd 100644 --- a/book.html +++ b/book.html @@ -25813,7 +25813,7 @@ This is a default behavior of the this tool does.</p> <div class="sect3"> <h4 id="_run_canary_test_as_daemon_mode"><a class="anchor" href="#_run_canary_test_as_daemon_mode"></a>144.1.5. Run canary test as daemon mode</h4> <div class="paragraph"> -<p>Run repeatedly with interval defined in option <code>-interval</code> whose default value is 6 seconds. +<p>Run repeatedly with interval defined in option <code>-interval</code> whose default value is 60 seconds. This daemon will stop itself and return non-zero error code if any error occurs, due to the default value of option -f is true.</p> </div> <div class="listingblock"> @@ -31429,61 +31429,9 @@ branches for past major/minor/maintenance releases and important features and bu </div> </div> <div class="sect2"> -<h3 id="_release_managers"><a class="anchor" href="#_release_managers"></a>167.2. Release Managers</h3> -<div class="paragraph"> -<p>Each maintained release branch has a release manager, who volunteers to coordinate new features and bug fixes are backported to that release. -The release managers are <a href="https://hbase.apache.org/team-list.html";>committers</a>. -If you would like your feature or bug fix to be included in a given release, communicate with that release manager. -If this list goes out of date or you can’t reach the listed person, reach out to someone else on the list.</p> -</div> -<div class="admonitionblock note"> -<table> -<tr> -<td class="icon"> -<i class="fa icon-note" title="Note"></i> -</td> -<td class="content"> -End-of-life releases are not included in this list. -</td> -</tr> -</table> -</div> -<table class="tableblock frame-all grid-all spread"> -<caption class="title">Table 20. Release Managers</caption> -<colgroup> -<col style="width: 50%;"> -<col style="width: 50%;"> -</colgroup> -<thead> -<tr> -<th class="tableblock halign-left valign-top">Release</th> -<th class="tableblock halign-left valign-top">Release Manager</th> -</tr> -</thead> -<tbody> -<tr> -<td class="tableblock halign-left valign-top"><p class="tableblock">1.2</p></td> -<td class="tableblock halign-left valign-top"><p class="tableblock">Sean Busbey</p></td> -</tr> -<tr> -<td class="tableblock halign-left valign-top"><p class="tableblock">1.3</p></td> -<td class="tableblock halign-left valign-top"><p class="tableblock">Mikhail Antonov</p></td> -</tr> -<tr> -<td class="tableblock halign-left valign-top"><p class="tableblock">1.4</p></td> -<td class="tableblock halign-left valign-top"><p class="tableblock">Andrew Purtell</p></td> -</tr> -<tr> -<td class="tableblock halign-left valign-top"><p class="tableblock">2.0</p></td> -<td class="tableblock halign-left valign-top"><p class="tableblock">Michael Stack</p></td> -</tr> -</tbody> -</table> -</div> -<div class="sect2"> -<h3 id="code.standards"><a class="anchor" href="#code.standards"></a>167.3. Code Standards</h3> +<h3 id="code.standards"><a class="anchor" href="#code.standards"></a>167.2. Code Standards</h3> <div class="sect3"> -<h4 id="_interface_classifications"><a class="anchor" href="#_interface_classifications"></a>167.3.1. Interface Classifications</h4> +<h4 id="_interface_classifications"><a class="anchor" href="#_interface_classifications"></a>167.2.1. Interface Classifications</h4> <div class="paragraph"> <p>Interfaces are classified both by audience and by stability level. These labels appear at the head of a class. @@ -31561,7 +31509,7 @@ Mark your new packages if publicly accessible.</p> </div> </div> <div class="sect3"> -<h4 id="common.patch.feedback"><a class="anchor" href="#common.patch.feedback"></a>167.3.2. Code Formatting Conventions</h4> +<h4 id="common.patch.feedback"><a class="anchor" href="#common.patch.feedback"></a>167.2.2. Code Formatting Conventions</h4> <div class="paragraph"> <p>Please adhere to the following guidelines so that your patches can be reviewed more quickly. These guidelines have been developed based upon common feedback on patches from new contributors.</p> @@ -31749,7 +31697,7 @@ If you are creating a new class that needs to implement this interface, do not f </div> </div> <div class="sect3"> -<h4 id="_garbage_collection_conserving_guidelines"><a class="anchor" href="#_garbage_collection_conserving_guidelines"></a>167.3.3. Garbage-Collection Conserving Guidelines</h4> +<h4 id="_garbage_collection_conserving_guidelines"><a class="anchor" href="#_garbage_collection_conserving_guidelines"></a>167.2.3. Garbage-Collection Conserving Guidelines</h4> <div class="paragraph"> <p>The following guidelines were borrowed from <a href="http://engineering.linkedin.com/performance/linkedin-feed-faster-less-jvm-garbage"; class="bare">http://engineering.linkedin.com/performance/linkedin-feed-faster-less-jvm-garbage</a>. Keep them in mind to keep preventable garbage collection to a minimum. Have a look @@ -31781,13 +31729,13 @@ these guidelines.</p> </div> </div> <div class="sect2"> -<h3 id="design.invariants"><a class="anchor" href="#design.invariants"></a>167.4. Invariants</h3> +<h3 id="design.invariants"><a class="anchor" href="#design.invariants"></a>167.3. Invariants</h3> <div class="paragraph"> <p>We don’t have many but what we have we list below. All are subject to challenge of course but until then, please hold to the rules of the road.</p> </div> <div class="sect3"> -<h4 id="design.invariants.zk.data"><a class="anchor" href="#design.invariants.zk.data"></a>167.4.1. No permanent state in ZooKeeper</h4> +<h4 id="design.invariants.zk.data"><a class="anchor" href="#design.invariants.zk.data"></a>167.3.1. No permanent state in ZooKeeper</h4> <div class="paragraph"> <p>ZooKeeper state should transient (treat it like memory). If ZooKeeper state is deleted, hbase should be able to recover and essentially be in the same state.</p> </div> @@ -31819,7 +31767,7 @@ Follow progress on this issue at <a href="https://issues.apache.org/jira/browse/ </div> </div> <div class="sect2"> -<h3 id="run.insitu"><a class="anchor" href="#run.insitu"></a>167.5. Running In-Situ</h3> +<h3 id="run.insitu"><a class="anchor" href="#run.insitu"></a>167.4. Running In-Situ</h3> <div class="paragraph"> <p>If you are developing Apache HBase, frequently it is useful to test your changes against a more-real cluster than what you find in unit tests. In this case, HBase can be run directly from the source in local-mode. @@ -31848,7 +31796,7 @@ Generally, the above command is just a good thing to try running first, if maven </div> </div> <div class="sect2"> -<h3 id="add.metrics"><a class="anchor" href="#add.metrics"></a>167.6. Adding Metrics</h3> +<h3 id="add.metrics"><a class="anchor" href="#add.metrics"></a>167.5. Adding Metrics</h3> <div class="paragraph"> <p>After adding a new feature a developer might want to add metrics. HBase exposes metrics using the Hadoop Metrics 2 system, so adding a new metric involves exposing that metric to the hadoop system. @@ -31858,14 +31806,14 @@ To get an in-depth look at the reasoning and structure of these classes you can To add a metric to an existing MBean follow the short guide below:</p> </div> <div class="sect3"> -<h4 id="_add_metric_name_and_function_to_hadoop_compat_interface"><a class="anchor" href="#_add_metric_name_and_function_to_hadoop_compat_interface"></a>167.6.1. Add Metric name and Function to Hadoop Compat Interface.</h4> +<h4 id="_add_metric_name_and_function_to_hadoop_compat_interface"><a class="anchor" href="#_add_metric_name_and_function_to_hadoop_compat_interface"></a>167.5.1. Add Metric name and Function to Hadoop Compat Interface.</h4> <div class="paragraph"> <p>Inside of the source interface the corresponds to where the metrics are generated (eg MetricsMasterSource for things coming from HMaster) create new static strings for metric name and description. Then add a new method that will be called to add new reading.</p> </div> </div> <div class="sect3"> -<h4 id="_add_the_implementation_to_both_hadoop_1_and_hadoop_2_compat_modules"><a class="anchor" href="#_add_the_implementation_to_both_hadoop_1_and_hadoop_2_compat_modules"></a>167.6.2. Add the Implementation to Both Hadoop 1 and Hadoop 2 Compat modules.</h4> +<h4 id="_add_the_implementation_to_both_hadoop_1_and_hadoop_2_compat_modules"><a class="anchor" href="#_add_the_implementation_to_both_hadoop_1_and_hadoop_2_compat_modules"></a>167.5.2. Add the Implementation to Both Hadoop 1 and Hadoop 2 Compat modules.</h4> <div class="paragraph"> <p>Inside of the implementation of the source (eg. MetricsMasterSourceImpl in the above example) create a new histogram, counter, gauge, or stat in the init method. @@ -31878,7 +31826,7 @@ For this the MetricsAssertHelper is provided.</p> </div> </div> <div class="sect2"> -<h3 id="git.best.practices"><a class="anchor" href="#git.best.practices"></a>167.7. Git Best Practices</h3> +<h3 id="git.best.practices"><a class="anchor" href="#git.best.practices"></a>167.6. Git Best Practices</h3> <div class="dlist"> <dl> <dt class="hdlist1">Avoid git merges.</dt> @@ -31895,7 +31843,7 @@ For this the MetricsAssertHelper is provided.</p> <p>Please contribute to this document if you think of other Git best practices.</p> </div> <div class="sect3"> -<h4 id="__code_rebase_all_git_branches_sh_code"><a class="anchor" href="#__code_rebase_all_git_branches_sh_code"></a>167.7.1. <code>rebase_all_git_branches.sh</code></h4> +<h4 id="__code_rebase_all_git_branches_sh_code"><a class="anchor" href="#__code_rebase_all_git_branches_sh_code"></a>167.6.1. <code>rebase_all_git_branches.sh</code></h4> <div class="paragraph"> <p>The <em>dev-support/rebase_all_git_branches.sh</em> script is provided to help keep your Git repository clean. Use the <code>-h</code> parameter to get usage instructions. @@ -31908,7 +31856,7 @@ The script checks the directory for sub-directory called <em>.git/</em>, before </div> </div> <div class="sect2"> -<h3 id="submitting.patches"><a class="anchor" href="#submitting.patches"></a>167.8. Submitting Patches</h3> +<h3 id="submitting.patches"><a class="anchor" href="#submitting.patches"></a>167.7. Submitting Patches</h3> <div class="paragraph"> <p>If you are new to submitting patches to open source or new to submitting patches to Apache, start by reading the <a href="https://commons.apache.org/patches.html";>On Contributing Patches</a> page from @@ -31918,7 +31866,7 @@ It provides a nice overview that applies equally to the Apache HBase Project. good read to understand development workflow.</p> </div> <div class="sect3"> -<h4 id="submitting.patches.create"><a class="anchor" href="#submitting.patches.create"></a>167.8.1. Create Patch</h4> +<h4 id="submitting.patches.create"><a class="anchor" href="#submitting.patches.create"></a>167.7.1. Create Patch</h4> <div class="paragraph"> <p>Make sure you review <a href="#common.patch.feedback">common.patch.feedback</a> for code style. If your patch @@ -32024,7 +31972,7 @@ Click on <b class="button">Cancel Patch</b> and then on <b class="button">Submit </div> </div> <div class="sect3"> -<h4 id="submitting.patches.tests"><a class="anchor" href="#submitting.patches.tests"></a>167.8.2. Unit Tests</h4> +<h4 id="submitting.patches.tests"><a class="anchor" href="#submitting.patches.tests"></a>167.7.2. Unit Tests</h4> <div class="paragraph"> <p>Always add and/or update relevant unit tests when making the changes. Make sure that new/changed unit tests pass locally before submitting the patch because it is faster @@ -32041,13 +31989,13 @@ See <a href="#hbase.tests">hbase.tests</a> for more information on tests.</p> </div> </div> <div class="sect3"> -<h4 id="_integration_tests"><a class="anchor" href="#_integration_tests"></a>167.8.3. Integration Tests</h4> +<h4 id="_integration_tests"><a class="anchor" href="#_integration_tests"></a>167.7.3. Integration Tests</h4> <div class="paragraph"> <p>Significant new features should provide an integration test in addition to unit tests, suitable for exercising the new feature at different points in its configuration space.</p> </div> </div> <div class="sect3"> -<h4 id="reviewboard"><a class="anchor" href="#reviewboard"></a>167.8.4. ReviewBoard</h4> +<h4 id="reviewboard"><a class="anchor" href="#reviewboard"></a>167.7.4. ReviewBoard</h4> <div class="paragraph"> <p>Patches larger than one screen, or patches that will be tricky to review, should go through <a href="https://reviews.apache.org";>ReviewBoard</a>.</p> </div> @@ -32090,7 +32038,7 @@ This attaches the ReviewBoard to the JIRA, for easy access.</p> </div> </div> <div class="sect3"> -<h4 id="_guide_for_hbase_committers"><a class="anchor" href="#_guide_for_hbase_committers"></a>167.8.5. Guide for HBase Committers</h4> +<h4 id="_guide_for_hbase_committers"><a class="anchor" href="#_guide_for_hbase_committers"></a>167.7.5. Guide for HBase Committers</h4> <div class="sect4"> <h5 id="_new_committers"><a class="anchor" href="#_new_committers"></a>New committers</h5> <div class="paragraph"> @@ -32370,21 +32318,21 @@ A committer should.</p> </div> </div> <div class="sect3"> -<h4 id="_dialog"><a class="anchor" href="#_dialog"></a>167.8.6. Dialog</h4> +<h4 id="_dialog"><a class="anchor" href="#_dialog"></a>167.7.6. Dialog</h4> <div class="paragraph"> <p>Committers should hang out in the #hbase room on irc.freenode.net for real-time discussions. However any substantive discussion (as with any off-list project-related discussion) should be re-iterated in Jira or on the developer list.</p> </div> </div> <div class="sect3"> -<h4 id="_do_not_edit_jira_comments"><a class="anchor" href="#_do_not_edit_jira_comments"></a>167.8.7. Do not edit JIRA comments</h4> +<h4 id="_do_not_edit_jira_comments"><a class="anchor" href="#_do_not_edit_jira_comments"></a>167.7.7. Do not edit JIRA comments</h4> <div class="paragraph"> <p>Misspellings and/or bad grammar is preferable to the disruption a JIRA comment edit causes: See the discussion at <a href="http://search-hadoop.com/?q=%5BReopened%5D+%28HBASE-451%29+Remove+HTableDescriptor+from+HRegionInfo&fc_project=HBase";>Re:(HBASE-451) Remove HTableDescriptor from HRegionInfo</a></p> </div> </div> </div> <div class="sect2"> -<h3 id="thirdparty"><a class="anchor" href="#thirdparty"></a>167.9. The hbase-thirdparty dependency and shading/relocation</h3> +<h3 id="thirdparty"><a class="anchor" href="#thirdparty"></a>167.8. The hbase-thirdparty dependency and shading/relocation</h3> <div class="paragraph"> <p>A new project was created for the release of hbase-2.0.0. It was called <code>hbase-thirdparty</code>. This project exists only to provide the main hbase @@ -32428,7 +32376,7 @@ in the hbase-thirdparty, use the hbase JIRA and mailing lists to post notice.</p </div> </div> <div class="sect2"> -<h3 id="hbase.archetypes.development"><a class="anchor" href="#hbase.archetypes.development"></a>167.10. Development of HBase-related Maven archetypes</h3> +<h3 id="hbase.archetypes.development"><a class="anchor" href="#hbase.archetypes.development"></a>167.9. Development of HBase-related Maven archetypes</h3> <div class="paragraph"> <p>The development of HBase-related Maven archetypes was begun with <a href="https://issues.apache.org/jira/browse/HBASE-14876";>HBASE-14876</a>. @@ -33430,27 +33378,6 @@ When the feature is ready for commit, 3 +1s from committers will get your featur See <a href="http://search-hadoop.com/m/asM982C5FkS1";>HBase, mail # dev - Thoughts about large feature dev branches</a></p> </div> -<div id="patchplusonepolicy" class="paragraph"> -<div class="title">Patch +1 Policy</div> -<p>The below policy is something we put in place 09/2012. -It is a suggested policy rather than a hard requirement. -We want to try it first to see if it works before we cast it in stone.</p> -</div> -<div class="paragraph"> -<p>Apache HBase is made of <a href="https://issues.apache.org/jira/projects/HBASE?selectedItem=com.atlassian.jira.jira-projects-plugin:components-page";>components</a>. -Components have one or more <a href="#owner">OWNER</a>s. -See the 'Description' field on the <a href="https://issues.apache.org/jira/projects/HBASE?selectedItem=com.atlassian.jira.jira-projects-plugin:components-page";>components</a> JIRA page for who the current owners are by component.</p> -</div> -<div class="paragraph"> -<p>Patches that fit within the scope of a single Apache HBase component require, at least, a +1 by one of the component’s owners before commit. -If owners are absent — busy or otherwise — two +1s by non-owners will suffice.</p> -</div> -<div class="paragraph"> -<p>Patches that span components need at least two +1s before they can be committed, preferably +1s by owners of components touched by the x-component patch (TODO: This needs tightening up but I think fine for first pass).</p> -</div> -<div class="paragraph"> -<p>Any -1 on a patch by anyone vetoes a patch; it cannot be committed until the justification for the -1 is addressed.</p> -</div> <div id="hbase.fix.version.in.jira" class="paragraph"> <div class="title">How to set fix version in JIRA on issue resolve</div> <p>Here is how <a href="http://search-hadoop.com/m/azemIi5RCJ1";>we agreed</a> to set versions in JIRA when we resolve an issue. @@ -33488,27 +33415,57 @@ We also are currently in violation of this basic tenet — repli <div class="sect1"> <h2 id="community.roles"><a class="anchor" href="#community.roles"></a>176. Community Roles</h2> <div class="sectionbody"> -<div id="owner" class="paragraph"> -<div class="title">Component Owner/Lieutenant</div> -<p>Component owners are listed in the description field on this Apache HBase JIRA <a href="https://issues.apache.org/jira/projects/HBASE?selectedItem=com.atlassian.jira.jira-projects-plugin:components-page";>components</a> page. -The owners are listed in the 'Description' field rather than in the 'Component Lead' field because the latter only allows us list one individual whereas it is encouraged that components have multiple owners.</p> -</div> +<div class="sect2"> +<h3 id="_release_managers"><a class="anchor" href="#_release_managers"></a>176.1. Release Managers</h3> <div class="paragraph"> -<p>Owners or component lieutenants are volunteers who are (usually, but not necessarily) expert in their component domain and may have an agenda on how they think their Apache HBase component should evolve.</p> +<p>Each maintained release branch has a release manager, who volunteers to coordinate new features and bug fixes are backported to that release. +The release managers are <a href="https://hbase.apache.org/team-list.html";>committers</a>. +If you would like your feature or bug fix to be included in a given release, communicate with that release manager. +If this list goes out of date or you can’t reach the listed person, reach out to someone else on the list.</p> </div> -<div class="olist arabic"> -<ol class="arabic"> -<li> -<p>Owners will try and review patches that land within their component’s scope.</p> -</li> -<li> -<p>If applicable, if an owner has an agenda, they will publish their goals or the design toward which they are driving their component</p> -</li> -</ol> +<div class="admonitionblock note"> +<table> +<tr> +<td class="icon"> +<i class="fa icon-note" title="Note"></i> +</td> +<td class="content"> +End-of-life releases are not included in this list. +</td> +</tr> +</table> </div> -<div class="paragraph"> -<p>If you would like to be volunteer as a component owner, just write the dev list and we’ll sign you up. -Owners do not need to be committers.</p> +<table class="tableblock frame-all grid-all spread"> +<caption class="title">Table 20. Release Managers</caption> +<colgroup> +<col style="width: 50%;"> +<col style="width: 50%;"> +</colgroup> +<thead> +<tr> +<th class="tableblock halign-left valign-top">Release</th> +<th class="tableblock halign-left valign-top">Release Manager</th> +</tr> +</thead> +<tbody> +<tr> +<td class="tableblock halign-left valign-top"><p class="tableblock">1.2</p></td> +<td class="tableblock halign-left valign-top"><p class="tableblock">Sean Busbey</p></td> +</tr> +<tr> +<td class="tableblock halign-left valign-top"><p class="tableblock">1.3</p></td> +<td class="tableblock halign-left valign-top"><p class="tableblock">Mikhail Antonov</p></td> +</tr> +<tr> +<td class="tableblock halign-left valign-top"><p class="tableblock">1.4</p></td> +<td class="tableblock halign-left valign-top"><p class="tableblock">Andrew Purtell</p></td> +</tr> +<tr> +<td class="tableblock halign-left valign-top"><p class="tableblock">2.0</p></td> +<td class="tableblock halign-left valign-top"><p class="tableblock">Michael Stack</p></td> +</tr> +</tbody> +</table> </div> </div> </div> @@ -37111,7 +37068,7 @@ The server will return cellblocks compressed using this same compressor as long <div id="footer"> <div id="footer-text"> Version 3.0.0-SNAPSHOT<br> -Last updated 2018-03-31 14:29:54 UTC +Last updated 2018-04-01 14:29:51 UTC </div> </div> </body>
http://git-wip-us.apache.org/repos/asf/hbase-site/blob/b707139a/bulk-loads.html ---------------------------------------------------------------------- diff --git a/bulk-loads.html b/bulk-loads.html index 53781c6..ec1a372 100644 --- a/bulk-loads.html +++ b/bulk-loads.html @@ -7,7 +7,7 @@ <head> <meta charset="UTF-8" /> <meta name="viewport" content="width=device-width, initial-scale=1.0" /> - <meta name="Date-Revision-yyyymmdd" content="20180331" /> + <meta name="Date-Revision-yyyymmdd" content="20180401" /> <meta http-equiv="Content-Language" content="en" /> <title>Apache HBase – Bulk Loads in Apache HBase (TM) @@ -296,7 +296,7 @@ under the License. --> <a href="https://www.apache.org/";>The Apache Software Foundation</a>. All rights reserved. - <li id="publishDate" class="pull-right">Last Published: 2018-03-31</li> + <li id="publishDate" class="pull-right">Last Published: 2018-04-01</li> </p> </div>
