While using indexer API to re-index the data there seems to be some sort of corruption occurring thereby requiring to reload the data.
While working on testing the nested search, I was not able to search the nested data. At which point I was told to verify that records were reindexed, and mappings at elastic are up to date. While using the following command e.g. to reindex WellLog data
curl --location --request POST 'https://4iqp6vd659.execute-api.us-west-2.amazonaws.com/api/indexer/v2/reindex?force_clean=true'
--header 'data-partition-id: osdu'
--header 'Content-Type: application/json'
--header 'Authorization: Bearer eyJraWQiOiIwekkwRHB5RzBZK3pUUTJpVlZ...'
--data-raw '{
"kind":"osdu:wks:work-product-component--WellLog:1.0.0"
}'
The response code: 200 OK
But I was still not able to access the nested data. Upon complaining to CSPs, I was told that data had to be reloaded as it got messed up when I made the reindex request.
This kind of behavior was seen in multiple CSP environments (AWS, IBM. Azure)
I understand that in the normal workflow when everything is set correctly one should not have to re-index. Reindexing is not part of the normal workflow performed by users. But when it is required to be performed, it should work correctly, and more importantly, it should not corrupt/mess up the existing data. @ChrisZhang @ethiraj @ashams_s @Wibben @Kateryna_Kurach @meenarathinavel @manishk @wladmirf @anujgupta @ankitsharma