[
https://issues.apache.org/jira/browse/HBASE-17649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15870768#comment-15870768
]
Hudson commented on HBASE-17649:
--------------------------------
SUCCESS: Integrated in Jenkins build HBase-1.2-JDK7 #102 (See
[https://builds.apache.org/job/HBase-1.2-JDK7/102/])
HBASE-17649 REST API for scan should return 410 when table is disabled (tedyu:
rev 81c0f24b9439d3393c7748b62e97e4117c4997d7)
* (edit)
hbase-rest/src/test/java/org/apache/hadoop/hbase/rest/TestScannerResource.java
* (edit)
hbase-rest/src/main/java/org/apache/hadoop/hbase/rest/ScannerResultGenerator.java
> REST API for scan should return 410 when table is disabled
> ----------------------------------------------------------
>
> Key: HBASE-17649
> URL: https://issues.apache.org/jira/browse/HBASE-17649
> Project: HBase
> Issue Type: Bug
> Reporter: Ted Yu
> Assignee: Ted Yu
> Fix For: 2.0.0, 1.4.0, 1.3.1, 1.2.5
>
> Attachments: 17649.branch-1.3.v1.txt, 17649.v1.txt
>
>
> Background:
> When scanning using REST API, if the table is disabled in the middle of the
> scan, code 410 (Gone) should be returned.
> Currently in 1.3 and lower releases, ScannerResultGenerator#next() doesn't
> handle TableNotEnabledException, leading to the exception being ignored and
> code 204 is returned to caller.
> This was first spotted by [~Apache9] when investigating HBASE-17603.
> Patch for HBASE-17603 contains fix for this problem.
> This issue fixes the bug for 1.3 and lower branches and adds test for
> branch-1 and master branch.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
