hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ted Yu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-17603) Rest api for scan should return 404 when table not exists
Date Thu, 09 Feb 2017 03:36:42 GMT

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

Ted Yu commented on HBASE-17603:
--------------------------------

The next() call would encounter exception in the above scenario.
In current releases, same behavior is expected.

> 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
>
>
> 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)

Mime
View raw message