Schema issueshttps://community.opengroup.org/osdu/platform/system/schema-service/-/issues2024-03-14T16:18:32Zhttps://community.opengroup.org/osdu/platform/system/schema-service/-/issues/142Content-Type returned doesn't match OpenAPI json2024-03-14T16:18:32ZShane HutchinsContent-Type returned doesn't match OpenAPI jsonOne note the Content-Type returned in the following doesn't match OpenAPI json:
* GET /api/schema-service/v1/schema
* PUT /api/schema-service/v1/schema
* POST /api/schema-service/v1/schema
* GET /api/schema-service/v1/schema/{id}
Rece...One note the Content-Type returned in the following doesn't match OpenAPI json:
* GET /api/schema-service/v1/schema
* PUT /api/schema-service/v1/schema
* POST /api/schema-service/v1/schema
* GET /api/schema-service/v1/schema/{id}
Received a response with 'application/json' Content-Type, but it is not declared in the schema.
`Defined content types: */*`
`curl -X GET -H 'Authorization: [Filtered]' -H 'data-partition-id: opendes' 'https://osdu-glab.msft-osdu-test.org/api/schema-service/v1/schema?authority=osdu&source=wks&entityType=wellbore&schemaVersionMajor=1&schemaVersionMinor=1&status=PUBLISHED&scope=INTERNAL&latestVersion=True&limit=10'`
Response status: 200
Response payload: `{"schemaInfos":[],"offset":0,"count":0,"totalCount":0}`M22 - Release 0.25Chad LeongShane HutchinsChad Leonghttps://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.22https://community.opengroup.org/osdu/platform/system/schema-service/-/issues/69Intermittent GET Schema endpoint response with 4042023-06-28T08:35:38ZNeelesh ThakurIntermittent GET Schema endpoint response with 404Indexer/Search consumers have reported issues that data block is not indexed for certain records.
While triaging the issue, we have found Schema service is responding with 404 when it receives multiple concurrent request in this case (p...Indexer/Search consumers have reported issues that data block is not indexed for certain records.
While triaging the issue, we have found Schema service is responding with 404 when it receives multiple concurrent request in this case (please take a look at logs below).
![Schema_Error](/uploads/e2eb86fb1697c46dc09fa3283e0133f1/Schema_Error.jpg)Aman VermaAman Verma