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 7AA2F200C16 for ; Thu, 9 Feb 2017 15:42:48 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 792CB160B6B; Thu, 9 Feb 2017 14:42:48 +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 C5551160B50 for ; Thu, 9 Feb 2017 15:42:47 +0100 (CET) Received: (qmail 19454 invoked by uid 500); 9 Feb 2017 14:42:46 -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 19327 invoked by uid 99); 9 Feb 2017 14:42:46 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 09 Feb 2017 14:42:46 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id D162FC3223 for ; Thu, 9 Feb 2017 14:42:45 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-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 (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id OfM72oyWJpa7 for ; Thu, 9 Feb 2017 14:42:45 +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 127DB5FB9A for ; Thu, 9 Feb 2017 14:42:45 +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 AF340E05BB for ; Thu, 9 Feb 2017 14:42:43 +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 38D0B21D69 for ; Thu, 9 Feb 2017 14:42:42 +0000 (UTC) Date: Thu, 9 Feb 2017 14:42:42 +0000 (UTC) From: "Ted Yu (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 14:42:48 -0000 [ https://issues.apache.org/jira/browse/HBASE-17603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15859596#comment-15859596 ] Ted Yu commented on HBASE-17603: -------------------------------- 204 is NO_CONTENT. I don't see it being referenced in our code base. Can you point me to where it is used ? > 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)