[ATLAS-1611] Regression: Incorrect error code for the negative tests. Returned: "500 server error", expected: "400 Bad Request"

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 0.8-incubating
• Fix Version/s: 0.8.1, 1.0.0
• Component/s: atlas-core
• Assignee: Sarath Subramanian
• Reporter: Ayub Pathan
• Created: 01/Mar/17 12:46
• Updated: 17/May/17 16:44
• Resolved: 28/Apr/17 00:03

Description

• Scenario-1: Creating an entity with invalidGUID results in "500 server error", expected response is "400 Bad Request"
  Sample json when posted to atlas results in 500 internal error,

        {
          "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference",
          "id":{
            "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
            "id":"invalid",
            "version":0,
            "typeName":"ComplexEntityTestColumnroshbaacqm",
            "state":"ACTIVE"
          },
          "typeName":"ComplexEntityTestColumnroshbaacqm",
          "values":{
            "name":"column1hlrfnjmmth"
          },
          "traitNames":[
  
          ],
          "traits":{
  
          },
          "systemAttributes":{
            "createdBy":null,
            "modifiedBy":null,
            "createdTime":null,
            "modifiedTime":null
          }
        }
  

• Scenario-2: Full update REST API call of an entity with request payload having unsupported value for a type(for example: for float type value is set as "str") results in "500 server error" but the expected response is "400 bad request".