Thanks to a feature in a AWS database migration to...
# troubleshoot
h
Thanks to a feature in a AWS database migration tool, we ended up with corrupted data in our GMS database. No biggie. Other than that we lose a lot of historical data, would there be an issue with doing the following in order to start almost from scratch: 1. Stop all ingestion 2. delete entries in the GMS database (excluding a set of urn-types, for example
dataHubPolicy
) 3. Run the index repopulation job 4. Start the ingestion again. Does this sound like a reasonable plan?