Inconsistency between aws and azure enriched fields
Using the below query
{
"kind": "opendes:osdu:*:0.2.1",
"query": "data.Data.IndividualTypeProperties.WellboreID:(\"srn:master-data/Wellbore:1083:\")",
"limit":100,
"offset":0,
"aggregateBy": "kind"
}
There are some extra fields include in the aws response that is not present in azure response.
The fields that are missing from the azure response appear to be some of the original fields that now have an enriched field equivalent.
azure_response.txt
awsResponse.txt