[
https://issues.apache.org/jira/browse/ASTERIXDB-2057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16138827#comment-16138827
]
ASF subversion and git services commented on ASTERIXDB-2057:
------------------------------------------------------------
Commit 78b1a694bb6d84a8298a1cb4986fa322f6ccc0ae in asterixdb's branch
refs/heads/master from [~idleft]
[ https://git-wip-us.apache.org/repos/asf?p=asterixdb.git;h=78b1a69 ]
[ASTERIXDB-2057][API] Add detailed error message for 500 in REST API
- user model changes: no
- storage format changes: no
- interface changes: no
Details:
1. Add error message to 500 response.
2. Specify proper content type for Ansible query execution script, so
LIKE % can be parsed properly.
3. Add semicolons to statements in create.sqlpp.
Change-Id: I17759141116a1baf878abf7d5ec70295a18946e8
Reviewed-on: https://asterix-gerrit.ics.uci.edu/1959
Sonar-Qube: Jenkins <jenk...@fulliautomatix.ics.uci.edu>
Tested-by: Jenkins <jenk...@fulliautomatix.ics.uci.edu>
Contrib: Jenkins <jenk...@fulliautomatix.ics.uci.edu>
Reviewed-by: Yingyi Bu <buyin...@gmail.com>
> 500 error from Query API needs to have more detailed information
> ----------------------------------------------------------------
>
> Key: ASTERIXDB-2057
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-2057
> Project: Apache AsterixDB
> Issue Type: Bug
> Reporter: Xikui Wang
>
> The current Ansible execute query script in TPCH benchmark sends query with
> default content-type which is application/x-www-form-urlencoded. This will
> cause the parse issue in queries contain LIKE %. This needs to be fixed by
> change content type to plain text, and add more detailed info for the 500
> error.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
