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 9D85F178F4 for ; Thu, 2 Jul 2015 23:07:06 +0000 (UTC) Received: (qmail 20474 invoked by uid 500); 2 Jul 2015 23:07:06 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 20424 invoked by uid 500); 2 Jul 2015 23:07:06 -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 20410 invoked by uid 99); 2 Jul 2015 23:07:06 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Jul 2015 23:07:06 +0000 Date: Thu, 2 Jul 2015 23:07:06 +0000 (UTC) From: "Enis Soztutar (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (HBASE-13561) ITBLL.Verify doesn't actually evaluate counters after job completes 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-13561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Enis Soztutar updated HBASE-13561: ---------------------------------- Fix Version/s: (was: 1.0.2) 1.0.3 > ITBLL.Verify doesn't actually evaluate counters after job completes > ------------------------------------------------------------------- > > Key: HBASE-13561 > URL: https://issues.apache.org/jira/browse/HBASE-13561 > Project: HBase > Issue Type: Bug > Components: integration tests > Affects Versions: 1.0.0, 2.0.0, 1.1.0, 0.98.12 > Reporter: Josh Elser > Assignee: Josh Elser > Fix For: 2.0.0, 0.98.14, 1.1.2, 1.3.0, 1.2.1, 1.0.3 > > > Was digging through ITBLL and noticed this oddity: > The {{Verify}} Tool doesn't actually call {{Verify#verify(long)}} like the {{Loop}} Tool does. Granted, it doesn't know the total number of KVs that were written given the current arguments, it's not even checking to see if there things like UNDEFINED records found. > It seems to me that {{Verify}} should really be doing *some* checking on the counters like {{Loop}} does and not just leaving it up to the visual inspection of whomever launched the task. > Am I missing something? -- This message was sent by Atlassian JIRA (v6.3.4#6332)