You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@drill.apache.org by "Hanifi Gunes (JIRA)" <ji...@apache.org> on 2015/02/11 01:19:12 UTC
[jira] [Created] (DRILL-2205) REST API should have a consistent way
of reporting failure in case a request fails
Hanifi Gunes created DRILL-2205:
-----------------------------------
Summary: REST API should have a consistent way of reporting failure in case a request fails
Key: DRILL-2205
URL: https://issues.apache.org/jira/browse/DRILL-2205
Project: Apache Drill
Issue Type: Improvement
Components: Client - HTTP
Affects Versions: 0.8.0
Reporter: Hanifi Gunes
Assignee: Jason Altekruse
In general, REST API does not do a good job reporting failures. Making a bogus HTTP call to create a new storage plugin such like
{code}
POST [drill-http-server-url]/storage/[storage-plugin-name]
{"name":"bogus"}
{code}
returns HTTP OK with no evidence that the former query failed except the string payload. This is quite a bit of problem for clients that must safely create or update storage plugin before attempting to execute queries as currently there is no unified definitive way to tell if a call succeeds w/o checking the response body. I presume test frameworks heavily rely on this functionality uploading plugin before each test run.
As part of DRILL-1357, our greater effort to re-design the REST API, we should make sure to define a consistent error message skeleton that is used across resources.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)