Schema issueshttps://community.opengroup.org/osdu/platform/system/schema-service/-/issues2023-06-15T13:06:31Zhttps://community.opengroup.org/osdu/platform/system/schema-service/-/issues/129AWS M18 GET /api/schema-service/v1/schema/{id}2023-06-15T13:06:31ZShane HutchinsAWS M18 GET /api/schema-service/v1/schema/{id}Received a response with 5xx status code: 500
{"error":{"code":500,"message":"Internal server error","errors":[{"domain":"global","reason":"internalError","message":"Internal server error"}]}}
I was really expecting a 4xx error, like a ...Received a response with 5xx status code: 500
{"error":{"code":500,"message":"Internal server error","errors":[{"domain":"global","reason":"internalError","message":"Internal server error"}]}}
I was really expecting a 4xx error, like a 404.
Run this curl command to reproduce this failure:
curl -X GET -H 'Authorization: Bearer TOKEN' -H 'data-partition-id: osdu' https://osdu.r3m18.preshiptesting.osdu.aws/api/schema-service/v1/schema/%1F
I could produce this in AWS. I could not reproduce this issue in Azure.https://community.opengroup.org/osdu/platform/system/schema-service/-/issues/123Incorrect status is being returned upon creating the schema that already exis...2023-05-31T11:42:03ZKamlesh TodaiIncorrect status is being returned upon creating the schema that already exists in the systemWhen one tries to create the schema that is already existing in the system, one gets the return error code of **400 - Bad request**. As per the API documentation, it is correct. But I think that the error code is misleading. The message ...When one tries to create the schema that is already existing in the system, one gets the return error code of **400 - Bad request**. As per the API documentation, it is correct. But I think that the error code is misleading. The message returned is also misleading. It returns "message": "Update/Create failed because schema id is present in another tenant, this is not true because the schema is present in the same tenant.
This is what one would expect, The return error code should be **409 Conflict** indicating that schema is already present. and the message should be "schema is present".M19 - Release 0.22