Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Sat, 11 Feb 2017 06:18:41 +0000 (UTC)
From: "Duo Zhang (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.13040800.1486422886000.54186.1486793921673@Atlassian.JIRA>
In-Reply-To: <JIRA.13040800.1486422886000@Atlassian.JIRA>
References: <JIRA.13040800.1486422886000@Atlassian.JIRA> <JIRA.13040800.1486422886749@jira-lw-us.apache.org>
Subject: [jira] [Commented] (HBASE-17603) REST api for scan should return
 404 when table does not exist
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Sat, 11 Feb 2017 06:18:45 -0000


    [ https://issues.apache.org/jira/browse/HBASE-17603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15862249#comment-15862249 ] 

Duo Zhang commented on HBASE-17603:
-----------------------------------

I had filed HBASE-17607 but IIRC you said please use HBASE-17603 to fix the problem so I resolve HBASE-17607 as duplicated by this issue and move the discussion here. So I think we should fix the problem in this issue. And IMO, the patch here only fix the UT, and is not useful for fixing the real problem. Please think a little further, let's fix the whole problem at once.

The first problem is, if we delete or disable the table when a scanner is on going, what will happen to our scanner? Or what do we want to give user?

Thanks.

> REST api for scan should return 404 when table does not exist
> -------------------------------------------------------------
>
>                 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, 17603.v4.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)