[
https://issues.apache.org/jira/browse/HBASE-17603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15862054#comment-15862054
]
Duo Zhang commented on HBASE-17603:
-----------------------------------
You can try open a scanner on an non-exists table and call next without the
patch here. The next call will return a 204. Maybe it is set by the rest
framework?
> 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)
