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 8D00F10A40 for ; Thu, 19 Sep 2013 19:24:11 +0000 (UTC) Received: (qmail 83839 invoked by uid 500); 19 Sep 2013 19:23:57 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 83712 invoked by uid 500); 19 Sep 2013 19:23:55 -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 83664 invoked by uid 99); 19 Sep 2013 19:23:55 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 19 Sep 2013 19:23:55 +0000 Date: Thu, 19 Sep 2013 19:23:55 +0000 (UTC) From: "Jesse Yates (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (HBASE-9584) Short-Circuit Coprocessor doesn't correctly lookup table when on server MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Jesse Yates created HBASE-9584: ---------------------------------- Summary: Short-Circuit Coprocessor doesn't correctly lookup table when on server Key: HBASE-9584 URL: https://issues.apache.org/jira/browse/HBASE-9584 Project: HBase Issue Type: Bug Reporter: Jesse Yates Assignee: Jesse Yates If the coprocessor isn't on the server hosting root/meta/the target HTable, it will fall back to doing the usual HConnection lookup. However, that call then calls the overloaded getHRegionConnection methods, which HBASE-9534 previously made unsupported for Coprocessors. The initial idea was to limit the number of paths that we could lookup a region, but it was just incorrectly done. -- 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