500 error on query request with non existing index

Bug #1351068 reported by Andrei V. Ostapenko on 2014-07-31
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MagnetoDB
Medium
Ajaya Agrawal

Bug Description

2014-07-31 17:17:53,255 Request: POST http://192.168.122.100:8480/v1/298474049dab4907928f95132bd05033/data/tables/testtempest1095305820/query
2014-07-31 17:17:53,256 Request Body: {"key_conditions": {"inumber": {"attribute_value_list": [{"N": "1"}], "comparison_operator": "EQ"}, "hash_attr": {"attribute_value_list": [{"S": "1"}], "comparison_operator": "EQ"}}, "index_name": "NON_EXISTING"}
2014-07-31 17:17:53,282 Response Status: 500
2014-07-31 17:17:53,283 Response Headers: {'date': 'Thu, 31 Jul 2014 21:17:53 GMT', 'content-length': '274', 'content-type': 'application/json', 'connection': 'close, close'}
2014-07-31 17:17:53,284 Response Body: {"explanation": "The server has either erred or is incapable of performing the requested operation.", "code": 500, "error": {"message": "index_name 'NON_EXISTING' isn't specified in the schema", "traceback": null, "type": "AssertionError"}, "title": "Internal Server Error"}
}}}

Changed in magnetodb:
milestone: none → juno-3
importance: Undecided → Medium
Ilya Sviridov (isviridov) wrote :

It has been fixed with refactoring of validation.
Thx ajayaa for verification.

Changed in magnetodb:
assignee: nobody → Ajaya Agrawal (ajayaa)
status: New → Fix Committed

ajayaa, thank you!

Changed in magnetodb:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers