http://git-wip-us.apache.org/repos/asf/hbase-site/blob/8e3b63ca/apache_hbase_reference_guide.pdfmarks ---------------------------------------------------------------------- diff --git a/apache_hbase_reference_guide.pdfmarks b/apache_hbase_reference_guide.pdfmarks index 15c5be6..a604da0 100644 --- a/apache_hbase_reference_guide.pdfmarks +++ b/apache_hbase_reference_guide.pdfmarks @@ -2,8 +2,8 @@ /Author (Apache HBase Team) /Subject () /Keywords () - /ModDate (D:20170626145009) - /CreationDate (D:20170626145009) + /ModDate (D:20170627145011) + /CreationDate (D:20170627145011) /Creator (Asciidoctor PDF 1.5.0.alpha.6, based on Prawn 1.2.1) /Producer () /DOCINFO pdfmark
http://git-wip-us.apache.org/repos/asf/hbase-site/blob/8e3b63ca/book.html ---------------------------------------------------------------------- diff --git a/book.html b/book.html index ede710c..c1376a3 100644 --- a/book.html +++ b/book.html @@ -27586,24 +27586,157 @@ FreeNode offers a web-based client, but most people prefer a native client, and If it’s either a new feature request, enhancement, or a bug, file a ticket.</p> </div> <div class="paragraph"> +<p>We track multiple types of work in JIRA:</p> +</div> +<div class="ulist"> +<ul> +<li> +<p>Bug: Something is broken in HBase itself.</p> +</li> +<li> +<p>Test: A test is needed, or a test is broken.</p> +</li> +<li> +<p>New feature: You have an idea for new functionality. It’s often best to bring +these up on the mailing lists first, and then write up a design specification +that you add to the feature request JIRA.</p> +</li> +<li> +<p>Improvement: A feature exists, but could be tweaked or augmented. It’s often +best to bring these up on the mailing lists first and have a discussion, then +summarize or link to the discussion if others seem interested in the +improvement.</p> +</li> +<li> +<p>Wish: This is like a new feature, but for something you may not have the +background to flesh out yourself.</p> +</li> +</ul> +</div> +<div class="paragraph"> +<p>Bugs and tests have the highest priority and should be actionable.</p> +</div> +<div class="sect3"> +<h4 id="_guidelines_for_reporting_effective_issues"><a class="anchor" href="#_guidelines_for_reporting_effective_issues"></a>143.4.1. Guidelines for reporting effective issues</h4> +<div class="ulist"> +<ul> +<li> +<p><strong>Search for duplicates</strong>: Your issue may have already been reported. Have a +look, realizing that someone else might have worded the summary differently.</p> +<div class="paragraph"> +<p>Also search the mailing lists, which may have information about your problem +and how to work around it. Don’t file an issue for something that has already +been discussed and resolved on a mailing list, unless you strongly disagree +with the resolution <strong>and</strong> are willing to help take the issue forward.</p> +</div> +<div class="ulist"> +<ul> +<li> +<p><strong>Discuss in public</strong>: Use the mailing lists to discuss what you’ve discovered +and see if there is something you’ve missed. Avoid using back channels, so +that you benefit from the experience and expertise of the project as a whole.</p> +</li> +<li> +<p><strong>Don’t file on behalf of others</strong>: You might not have all the context, and you +don’t have as much motivation to see it through as the person who is actually +experiencing the bug. It’s more helpful in the long term to encourage others +to file their own issues. Point them to this material and offer to help out +the first time or two.</p> +</li> +<li> +<p><strong>Write a good summary</strong>: A good summary includes information about the problem, +the impact on the user or developer, and the area of the code.</p> +<div class="ulist"> +<ul> +<li> +<p>Good: <code>Address new license dependencies from hadoop3-alpha4</code></p> +</li> +<li> +<p>Room for improvement: <code>Canary is broken</code></p> +<div class="paragraph"> +<p>If you write a bad title, someone else will rewrite it for you. This is time +they could have spent working on the issue instead.</p> +</div> +</li> +</ul> +</div> +</li> +<li> +<p><strong>Give context in the description</strong>: It can be good to think of this in multiple +parts:</p> +<div class="ulist"> +<ul> +<li> +<p>What happens or doesn’t happen?</p> +</li> +<li> +<p>How does it impact you?</p> +</li> +<li> +<p>How can someone else reproduce it?</p> +</li> +<li> +<p>What would "fixed" look like?</p> +<div class="paragraph"> +<p>You don’t need to know the answers for all of these, but give as much +information as you can. If you can provide technical information, such as a +Git commit SHA that you think might have caused the issue or a build failure +on builds.apache.org where you think the issue first showed up, share that +info.</p> +</div> +</li> +</ul> +</div> +</li> +<li> +<p><strong>Fill in all relevant fields</strong>: These fields help us filter, categorize, and +find things.</p> +</li> +<li> +<p><strong>One bug, one issue, one patch</strong>: To help with back-porting, don’t split issues +or fixes among multiple bugs.</p> +</li> +<li> +<p><strong>Add value if you can</strong>: Filing issues is great, even if you don’t know how to +fix them. But providing as much information as possible, being willing to +triage and answer questions, and being willing to test potential fixes is even +better! We want to fix your issue as quickly as you want it to be fixed.</p> +</li> +<li> +<p><strong>Don’t be upset if we don’t fix it</strong>: Time and resources are finite. In some +cases, we may not be able to (or might choose not to) fix an issue, especially +if it is an edge case or there is a workaround. Even if it doesn’t get fixed, +the JIRA is a public record of it, and will help others out if they run into +a similar issue in the future.</p> +</li> +</ul> +</div> +</li> +</ul> +</div> +</div> +<div class="sect3"> +<h4 id="_working_on_an_issue"><a class="anchor" href="#_working_on_an_issue"></a>143.4.2. Working on an issue</h4> +<div class="paragraph"> <p>To check for existing issues which you can tackle as a beginner, search for <a href="https://issues.apache.org/jira/issues/?jql=project%20%3D%20HBASE%20AND%20labels%20in%20(beginner)">issues in JIRA tagged with the label 'beginner'</a>.</p> </div> <div class="ulist"> +<div class="title">JIRA Priorites</div> <ul> <li> -<p>.JIRA PrioritiesBlocker: Should only be used if the issue WILL cause data loss or cluster instability reliably.</p> +<p><strong>Blocker</strong>: Should only be used if the issue WILL cause data loss or cluster instability reliably.</p> </li> <li> -<p>Critical: The issue described can cause data loss or cluster instability in some cases.</p> +<p><strong>Critical</strong>: The issue described can cause data loss or cluster instability in some cases.</p> </li> <li> -<p>Major: Important but not tragic issues, like updates to the client API that will add a lot of much-needed functionality or significant bugs that need to be fixed but that don’t cause data loss.</p> +<p><strong>Major</strong>: Important but not tragic issues, like updates to the client API that will add a lot of much-needed functionality or significant bugs that need to be fixed but that don’t cause data loss.</p> </li> <li> -<p>Minor: Useful enhancements and annoying but not damaging bugs.</p> +<p><strong>Minor</strong>: Useful enhancements and annoying but not damaging bugs.</p> </li> <li> -<p>Trivial: Useful enhancements but generally cosmetic.</p> +<p><strong>Trivial</strong>: Useful enhancements but generally cosmetic.</p> </li> </ul> </div> @@ -27625,6 +27758,7 @@ code snippet </div> </div> </div> +</div> <div class="sect1"> <h2 id="repos"><a class="anchor" href="#repos"></a>144. Apache HBase Repositories</h2> <div class="sectionbody"> http://git-wip-us.apache.org/repos/asf/hbase-site/blob/8e3b63ca/bulk-loads.html ---------------------------------------------------------------------- diff --git a/bulk-loads.html b/bulk-loads.html index 03439da..e784b48 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="20170626" /> + <meta name="Date-Revision-yyyymmdd" content="20170627" /> <meta http-equiv="Content-Language" content="en" /> <title>Apache HBase – Bulk Loads in Apache HBase (TM) @@ -311,7 +311,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: 2017-06-26</li> + <li id="publishDate" class="pull-right">Last Published: 2017-06-27</li> </p> </div>
