Need to decide whether the aggregations field is required or not in the response body, even if the field is null. Need to have consistent behavior.
At present, the test is changed to drop the checking of the field in the postman collection "Search API CI-CD v1.7.postman_collection.json" of testing Platform validation project.
One needs to decided whether that field is required or not. This check is being done while searching for seismic data: {{data-partition-id}}:osdu:seismic-acquisition-project:{{standard_schema_version}} {{data-partition-id}}:osdu:seismic-processing-project:{{standard_schema_version}} {{data-partition-id}}:osdu:seismictracedata-wpc:{{standard_schema_version}} {{data-partition-id}}:osdu:seismichorizon-wpc:{{standard_schema_version}}
using following schema const schema = { "required": [ "results", "aggregations", "totalCount" ], "properties": { "results": { "id": "#/properties/results", "type": "array" }, "aggregations": { "
id": "#/properties/aggregations", "type": ["array", "null"] }, "totalCount": { "$id": "#/properties/totalCount", "type": "integer" } }
On IBM, Azure platform the field is being returned (as null) in the results on GCP I cannot tell as the tests are failing because there is no data (But, Dmitriy Rudko comment above suggest that it returns the field) On AWS the filed is not being returned. Later on @spencer noted that in some environments for Azure the field was not being returned also. All CSPs need to have consistent behavior.
Linking with https://community.opengroup.org/osdu/platform/testing/-/issues/10