[Bug-fix] Translate JSONException to 400 instead of 500#3833
Conversation
Signed-off-by: Jialiang Liang <jiallian@amazon.com>
Signed-off-by: Jialiang Liang <jiallian@amazon.com>
Signed-off-by: Jialiang Liang <jiallian@amazon.com>
dai-chen
left a comment
There was a problem hiding this comment.
Meanwhile do you have error stacktrace? I'm thinking another option is to figure out why this JSON exception is not captured.
Here we go: |
Signed-off-by: Jialiang Liang <jiallian@amazon.com>
Got it. In this case, we can capture it in parse payload method for SQL and PPL separately. The reason is this |
Signed-off-by: Jialiang Liang <jiallian@amazon.com>
Signed-off-by: Jialiang Liang <jiallian@amazon.com>
noCharger
left a comment
There was a problem hiding this comment.
@RyanL1997 should this backport to 2.x and 2.19-dev?
|
I don't think this one can fall into either the criteria of maintenance and critical bugfix. We can if we consider to include this into the future patch of 2.19.x. |
Description
Translate JSONException to 400 instead of 500
Related Issues
JSONException#3832Check List
--signoff.By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.