Return-Path: X-Original-To: apmail-hbase-issues-archive@www.apache.org Delivered-To: apmail-hbase-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 134C318C0B for ; Tue, 25 Aug 2015 01:57:46 +0000 (UTC) Received: (qmail 90515 invoked by uid 500); 25 Aug 2015 01:57:45 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 90467 invoked by uid 500); 25 Aug 2015 01:57:45 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 90455 invoked by uid 99); 25 Aug 2015 01:57:45 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 25 Aug 2015 01:57:45 +0000 Date: Tue, 25 Aug 2015 01:57:45 +0000 (UTC) From: "Hadoop QA (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-13696) Prune retired hbase versions from ref guide prereq support tables MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HBASE-13696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14710438#comment-14710438 ] Hadoop QA commented on HBASE-13696: ----------------------------------- {color:red}-1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12752096/HBASE-13696.2.patch against master branch at commit d0873f5a8cc060adbc5a1ae0ed52b84a8942a868. ATTACHMENT ID: 12752096 {color:green}+1 @author{color}. The patch does not contain any @author tags. {color:green}+0 tests included{color}. The patch appears to be a documentation, build, or dev-support patch that doesn't require tests. {color:green}+1 hadoop versions{color}. The patch compiles with all supported hadoop versions (2.4.0 2.4.1 2.5.0 2.5.1 2.5.2 2.6.0 2.7.0) {color:green}+1 javac{color}. The applied patch does not increase the total number of javac compiler warnings. {color:green}+1 protoc{color}. The applied patch does not increase the total number of protoc compiler warnings. {color:green}+1 javadoc{color}. The javadoc tool did not generate any warning messages. {color:green}+1 checkstyle{color}. The applied patch does not increase the total number of checkstyle errors {color:green}+1 findbugs{color}. The patch does not introduce any new Findbugs (version 2.0.3) warnings. {color:green}+1 release audit{color}. The applied patch does not increase the total number of release audit warnings. {color:red}-1 lineLengths{color}. The patch introduces the following lines longer than 100: +Coprocessors details are posted at link:https://blogs.apache.org/hbase/entry/coprocessor_introduction[Blog Overview of CoProcessors]. +You can override the default split policy using a custom link:http://hbase.apache.org/apidocs/org/apache/hadoop/hbase/regionserver/RegionSplitPolicy.html[RegionSplitPolicy]. Typically a custom split policy should extend +The default split policy can be overwritten using a custom link:http://hbase.apache.org/apidocs/org/apache/hadoop/hbase/regionserver/RegionSplitPolicy.html[RegionSplitPolicy]. Typically a custom split policy should extend HBase's default split policy: link:http://hbase.apache.org/apidocs/org/apache/hadoop/hbase/regionserver/ConstantSizeRegionSplitPolicy.html[ConstantSizeRegionSplitPolicy]. +* `hbase.hstore.compaction.min` (files) Minimum number of StoreFiles per Store to be selected for a compaction to occur (default 2). +HBase also offers `org.apache.hadoop.hbase.util.RegionSplitter`, providing a network-IO-safe rolling split of all regions. +The above will build against whatever explicit Hadoop 1.x version we have in our _pom.xml_ as our '1.0' version. +if you pass +hadoop.profile=2.0+ when building hadoop 0.98; just drop the hadoop.profile stipulation in this case to get your build to run again. +HBase 0.98 still runs on Hadoop 1.x or Hadoop 2.x, but HBase 0.98 deprecates use of Hadoop 1. HBase 1.x will _not_ run on Hadoop 1.x. +In the following procedures, we make a distinction between HBase 1.x builds and the awkward process involved building HBase 0.98 for either Hadoop 1 or Hadoop 2 targets. +At this point you should tag the previous release branch (ex: 1.1.0) with the new point release tag (e.g. {color:green}+1 site{color}. The mvn post-site goal succeeds with this patch. {color:red}-1 core tests{color}. The patch failed these unit tests: org.apache.hadoop.hbase.TestIOFencing Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/15231//testReport/ Release Findbugs (version 2.0.3) warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/15231//artifact/patchprocess/newFindbugsWarnings.html Checkstyle Errors: https://builds.apache.org/job/PreCommit-HBASE-Build/15231//artifact/patchprocess/checkstyle-aggregate.html Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/15231//console This message is automatically generated. > Prune retired hbase versions from ref guide prereq support tables > ----------------------------------------------------------------- > > Key: HBASE-13696 > URL: https://issues.apache.org/jira/browse/HBASE-13696 > Project: HBase > Issue Type: Task > Reporter: Sean Busbey > Assignee: Gabor Liptak > Labels: beginner > Attachments: HBASE-13696.1.patch, HBASE-13696.2.patch > > > the java table still contains HBase 0.96, and the Hadoop table still has HBase 0.92 and 0.96. We should remove these. Their details can still be found in their last release. -- This message was sent by Atlassian JIRA (v6.3.4#6332)