Search does not seem to be working as expected in pre-ship R3 M14 GCP environment.
While performing the test for Storage (Create-Update-Retrieve) & Unit Conversion I find that Search API does not seem to be working as expected in the pre-ship R3 M14 GCP environment.
I create a record using storage API, I can retrieve the record using storage API
curl --location --request GET 'https://preship.gcp.gnrg-osdu.projects.epam.com/api/storage/v2/records/odesprod:master-data--SeismicAcquisitionSurvey:Autotest_999704543963' \ --header 'data-partition-id: odesprod' \ --header 'Accept: application/json' \ --header 'Authorization: Bearer ya29.a0Aa4xr...KA0165'
Response:
{
"data": {
"Purpose": "Acquisition for Volve",
"SeismicGeometryTypeID": "odesprod:reference-data--SeismicGeometryType:3D:",
...
"FoldCount": 120,
"VesselNames": [
"GECO ANGLER"
]
},
"meta": [
{
...
},
{
"kind": "Unit",
"name": "ft",
...
}
],
**"id": "odesprod:master-data--SeismicAcquisitionSurvey:Autotest_999704543963"**,
"version": 1667319211819809,
"kind": "odesprod:wks:master-data--SeismicAcquisitionSurvey:1.0.0",
"acl": {
...
},
"legal": {
...
},
"createUser": "preshipping_test_user@osdu-gcp.go3-nrg.projects.epam.com",
"createTime": "2022-11-01T16:13:33.370Z"
}
when I try to use search API to get the record, it is not returning that record.
curl --location --request POST 'https://preship.gcp.gnrg-osdu.projects.epam.com/api/search/v2/query' \ --header 'Content-Type: application/json' \ --header 'data-partition-id: odesprod' \ --header 'Authorization: Bearer ya29.a0Aa4xr....KA0165' \ --data-raw '{ "kind": "odesprod:wks:master-data--SeismicAcquisitionSurvey:1.0.0", "query": **"id: \"odesprod:master-data--SeismicAcquisitionSurvey:Autotest_999704543963\"**" }'
Response:
{
"results": [],
"aggregations": [],
"totalCount": 0
}
I have tried
curl --location --request POST 'https://preship.gcp.gnrg-osdu.projects.epam.com/api/search/v2/query' \ --header 'Content-Type: application/json' \ --header 'data-partition-id: odesprod' \ --header 'Authorization: Bearer ya29.a0Aa4xr...KA0165' \ --data-raw '{ "kind": "odesprod:wks:master-data--SeismicAcquisitionSurvey:1.0.0", "query": **"*"** }'
In the last case I do get the records, but not the one (odesprod:master-data--SeismicAcquisitionSurvey:Autotest_999704543963) that was inserted using storage API (edited)
This workflow is working in AWS and Azure R3 M14 environment