hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-17649) REST API for scan should return 410 when table is disabled
Date Wed, 15 Feb 2017 20:07:41 GMT

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

Hudson commented on HBASE-17649:
--------------------------------

SUCCESS: Integrated in Jenkins build HBase-1.3-JDK7 #105 (See [https://builds.apache.org/job/HBase-1.3-JDK7/105/])
HBASE-17649 REST API for scan should return 410 when table is disabled (tedyu: rev a3d021aec5583456ee2bf306f796ba89fbe95f71)
* (edit) hbase-rest/src/main/java/org/apache/hadoop/hbase/rest/ScannerResultGenerator.java
* (edit) hbase-rest/src/test/java/org/apache/hadoop/hbase/rest/TestScannerResource.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
>         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)

Mime
View raw message