Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 16E90200C24 for ; Thu, 9 Feb 2017 06:12:46 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 15CD7160B6A; Thu, 9 Feb 2017 05:12:46 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 6101D160B67 for ; Thu, 9 Feb 2017 06:12:45 +0100 (CET) Received: (qmail 83558 invoked by uid 500); 9 Feb 2017 05:12:44 -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 83543 invoked by uid 99); 9 Feb 2017 05:12:44 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 09 Feb 2017 05:12:44 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 249EE1A008C for ; Thu, 9 Feb 2017 05:12:44 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 tagged_above=-999 required=6.31 tests=[KAM_LAZY_DOMAIN_SECURITY=1, RP_MATCHES_RCVD=-2.999] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id EH2ugQH1ypoP for ; Thu, 9 Feb 2017 05:12:43 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 001645F298 for ; Thu, 9 Feb 2017 05:12:42 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 0C1E3E0485 for ; Thu, 9 Feb 2017 05:12:42 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id BD6D621D66 for ; Thu, 9 Feb 2017 05:12:41 +0000 (UTC) Date: Thu, 9 Feb 2017 05:12:41 +0000 (UTC) From: "Duo Zhang (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-17603) Rest api for scan should return 404 when table not exists MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Thu, 09 Feb 2017 05:12:46 -0000 [ https://issues.apache.org/jira/browse/HBASE-17603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15859037#comment-15859037 ] Duo Zhang commented on HBASE-17603: ----------------------------------- My concern is, even without HBASE-17508, what if we delete the table after we get the scanner? Now the http code returned is 204, which is not expected as this means the table exists but does not have any data. We need to handle this. > Rest api for scan should return 404 when table not exists > --------------------------------------------------------- > > Key: HBASE-17603 > URL: https://issues.apache.org/jira/browse/HBASE-17603 > Project: HBase > Issue Type: Bug > Components: REST, scan > Affects Versions: 2.0.0, 1.4.0 > Reporter: Ted Yu > Priority: Blocker > Fix For: 2.0.0, 1.4.0 > > Attachments: 17603.v1.txt, 17603.v3.txt > > > This was the first Jenkins build where TestScannerResource#testTableDoesNotExist started failing. > https://builds.apache.org/job/HBase-1.4/612/jdk=JDK_1_8,label=Hadoop/testReport/junit/org.apache.hadoop.hbase.rest/TestScannerResource/testTableDoesNotExist/ > The test failure can be reproduced locally. > The test failure seemed to start after HBASE-17508 went in. > The problem is introduced after HBASE-17508. After HBASE-17508 we will not contact RS when getScanner. So for rest, get scanner will not return 404 either. But we should get a 404 when fetching data from the scanner but now it will return 204. -- This message was sent by Atlassian JIRA (v6.3.15#6346)