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 04362104CF for ; Mon, 29 Apr 2013 23:18:25 +0000 (UTC) Received: (qmail 78350 invoked by uid 500); 29 Apr 2013 23:18:20 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 78309 invoked by uid 500); 29 Apr 2013 23:18:20 -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 78273 invoked by uid 99); 29 Apr 2013 23:18:20 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 29 Apr 2013 23:18:20 +0000 Date: Mon, 29 Apr 2013 23:18:20 +0000 (UTC) From: "Chris Trezzo (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (HBASE-8460) [replication] Fix the three TODOs in TestReplicationStateBasic.testReplicationQueues MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Chris Trezzo created HBASE-8460: ----------------------------------- Summary: [replication] Fix the three TODOs in TestReplicationStateBasic.testReplicationQueues Key: HBASE-8460 URL: https://issues.apache.org/jira/browse/HBASE-8460 Project: HBase Issue Type: Bug Components: Replication Reporter: Chris Trezzo Assignee: Chris Trezzo Priority: Minor Fix For: 0.95.1 There are three TODO's in TestReplicationStateBasic.testReplicationQueues. 1. Possible NPE when getLogPosition is called on a Bogus HLog file. 2. The assertion that tested setting a log position on a bogus file was commented out. 3. When claimQueues is given the regionserver znode for itself, it will try to copy its own queues. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira