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 BF4431774E for ; Tue, 10 Feb 2015 05:12:35 +0000 (UTC) Received: (qmail 56710 invoked by uid 500); 10 Feb 2015 05:12:35 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 56664 invoked by uid 500); 10 Feb 2015 05:12:35 -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 56653 invoked by uid 99); 10 Feb 2015 05:12:35 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 10 Feb 2015 05:12:35 +0000 Date: Tue, 10 Feb 2015 05:12:35 +0000 (UTC) From: "Hadoop QA (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-12585) Fix refguide so it does hbase 1.0 style API everywhere with callout on how we used to do it in pre-1.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HBASE-12585?page=3Dcom.atlassia= n.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D143= 13583#comment-14313583 ]=20 Hadoop QA commented on HBASE-12585: ----------------------------------- {color:red}-1 overall{color}. Here are the results of testing the latest a= ttachment=20 http://issues.apache.org/jira/secure/attachment/12697648/HBASE-12585.patc= h against master branch at commit 9283b93e225edfaddbb8b24dd1b8214bcd328e97. ATTACHMENT ID: 12697648 {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 docum= entation patch that doesn't require tests. {color:green}+1 javac{color}. The applied patch does not increase the = total number of javac compiler warnings. {color:green}+1 javac{color}. The applied patch does not increase the = total number of javac 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 incre= ase the total number of release audit warnings. {color:red}-1 lineLengths{color}. The patch introduces the following l= ines longer than 100: +For more information about how connections are handled in the HBase cl= ient, see link:http://hbase.apache.org/apidocs/org/apache/hadoop/hbase/clie= nt/ConnectionFactory.html[ConnectionFactory]. +For applications which require high-end multithreaded access (e.g., web-se= rvers or application servers that may serve many application threads in a s= ingle JVM), you can pre-create a `CConnection`, as shown in the following e= xample: +Previous versions of this guide discussed `HTablePool`, which was deprecat= ed in HBase 0.94, 0.95, and 0.96, and removed in 0.98.1, by link:https://is= sues.apache.org/jira/browse/HBASE-6580[HBASE-6500], or `HConnection`, which= is deprecated in HBase 1.0 by `Connection`. +Please use link:http://hbase.apache.org/apidocs/org/apache/hadoop/hbase/cl= ient/Connection.html[Connection] instead. +If <> is turned off on link:http://hbase.apac= he.org/apidocs/org/apache/hadoop/hbase/client/Table.html[Table], ``Put``s a= re sent to RegionServers when the writebuffer is filled. +For fine-grained control of batching of ``Put``s or ``Delete``s, see the l= ink:http://hbase.apache.org/apidocs/org/apache/hadoop/hbase/client/Table.ht= ml#batch%28java.util.List%29[batch] methods on Table. +* Region (move, assign, unassign) For example, when the `Admin` method `di= sableTable` is invoked, it is serviced by the Master server. +* Region (splitRegion, compactRegion, etc.) For example, when the `Admin` = method `majorCompact` is invoked on a table, the client is actually iterati= ng through all regions for the specified table and requesting a major compa= ction directly to each region. + The timeout (in microseconds), before secondary fallback RPC=C3=A2= =C2=80=C2=99s are submitted for multi-get requests (Table.get(List)) w= ith Consistency.TIMELINE to the secondary replicas of the regions. Defaults= to 10ms. Setting this lower will increase the number of RPC=C3=A2=C2=80=C2= =99s, but will lower the p99 latencies. +If multiple ZooKeeper instances make up your ZooKeeper ensemble, they may = be specified in a comma-separated list (just as in the _hbase-site.xml_ fil= e). This populated `Configuration` instance can then be passed to an link:h= ttp://hbase.apache.org/apidocs/org/apache/hadoop/hbase/cl.html[Table], and = so on. {color:green}+1 site{color}. The mvn site goal succeeds with this patch. {color:red}-1 core tests{color}. The patch failed these unit tests: =20 {color:red}-1 core zombie tests{color}. There are 1 zombie test(s): = =09at org.apache.hadoop.hbase.TestChoreService.testCorePoolIncrease(TestCho= reService.java:420) Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/12747//te= stReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/1274= 7//artifact/patchprocess/newPatchFindbugsWarningshbase-protocol.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/1274= 7//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/1274= 7//artifact/patchprocess/newPatchFindbugsWarningshbase-thrift.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/1274= 7//artifact/patchprocess/newPatchFindbugsWarningshbase-server.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/1274= 7//artifact/patchprocess/newPatchFindbugsWarningshbase-common.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/1274= 7//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/1274= 7//artifact/patchprocess/newPatchFindbugsWarningshbase-rest.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/1274= 7//artifact/patchprocess/newPatchFindbugsWarningshbase-examples.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/1274= 7//artifact/patchprocess/newPatchFindbugsWarningshbase-client.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/1274= 7//artifact/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/1274= 7//artifact/patchprocess/newPatchFindbugsWarningshbase-annotations.html Checkstyle Errors: https://builds.apache.org/job/PreCommit-HBASE-Build/1274= 7//artifact/patchprocess/checkstyle-aggregate.html Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/12747= //console This message is automatically generated. > Fix refguide so it does hbase 1.0 style API everywhere with callout on ho= w we used to do it in pre-1.0 > -------------------------------------------------------------------------= ----------------------------- > > Key: HBASE-12585 > URL: https://issues.apache.org/jira/browse/HBASE-12585 > Project: HBase > Issue Type: Bug > Components: documentation > Reporter: stack > Assignee: Misty Stanley-Jones > Fix For: 1.0.1, 1.1.0 > > Attachments: HBASE-12585.patch > > > Over in HBASE-12400, made a start on this project writing up how the new = HBase 1.0 API looks. I started in on the refguide removing all HTable refe= rences replacing with new style and in the hbase client chapter added leado= ff that has users go get a cluster Connection first.... > Doing a thorough job of rinsing the doc of old style foregrounding the ne= w mode is a big job. > [~misty] Any chance of help on this one? Thanks boss. -- This message was sent by Atlassian JIRA (v6.3.4#6332)