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 9AB3117D52 for ; Sat, 23 May 2015 10:46:17 +0000 (UTC) Received: (qmail 5711 invoked by uid 500); 23 May 2015 10:46:17 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 5660 invoked by uid 500); 23 May 2015 10:46:17 -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 5649 invoked by uid 99); 23 May 2015 10:46:17 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 23 May 2015 10:46:17 +0000 Date: Sat, 23 May 2015 10:46:17 +0000 (UTC) From: "Hadoop QA (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-13754) Allow non KeyValue Cell types also to oswrite 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-13754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14557274#comment-14557274 ] Hadoop QA commented on HBASE-13754: ----------------------------------- {color:red}-1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12734999/HBASE-13754.patch against master branch at commit e93e1ea73c6ce5f632636c613068ddd877ebb60d. ATTACHMENT ID: 12734999 {color:green}+1 @author{color}. The patch does not contain any @author tags. {color:red}-1 tests included{color}. The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch. {color:green}+1 hadoop versions{color}. The patch compiles with all supported hadoop versions (2.4.1 2.5.2 2.6.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:green}+1 lineLengths{color}. The patch does not introduce lines longer than 100 {color:green}+1 site{color}. The mvn site goal succeeds with this patch. {color:green}+1 core tests{color}. The patch passed unit tests in . Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/14159//testReport/ Release Findbugs (version 2.0.3) warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/14159//artifact/patchprocess/newFindbugsWarnings.html Checkstyle Errors: https://builds.apache.org/job/PreCommit-HBASE-Build/14159//artifact/patchprocess/checkstyle-aggregate.html Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/14159//console This message is automatically generated. > Allow non KeyValue Cell types also to oswrite > --------------------------------------------- > > Key: HBASE-13754 > URL: https://issues.apache.org/jira/browse/HBASE-13754 > Project: HBase > Issue Type: Sub-task > Components: Scanners > Reporter: Anoop Sam John > Assignee: Anoop Sam John > Fix For: 2.0.0 > > Attachments: HBASE-13754.patch > > > While making the cellblock for returning data to client, we have to write the cell data into an OutputStream. KeyValue has a static oswrite() method with which it can write data in one go. (KeyValue components are in a single byte[]). For other cell implementation, we will call getXXXLength() and getXXXArray() and write each component one after the other. This is not efficient as the KeyValue way. In fact other cell impls also may have one contigous byte[] backing for keys atleast. (See ClonedSeekerState) We can optimize for such Cells also. -- This message was sent by Atlassian JIRA (v6.3.4#6332)