Hi Team, We have certain entities emitted to Datah...
# troubleshoot
b
Hi Team, We have certain entities emitted to Datahub initially under wrong env/cluster called PRD, instead of PROD. We tried to delete these entities as per the documentation given. We used delete command with option --env PRD, to delete all entities under the env PRD, but this doesn't work and it shows zero entities fetched. We also tried to delete one PRD entity using --urn <URN>, but even though it showed as "deleted" , the entity shows up while using GET on the same URN ( where as hard delete works on other entities with valid env like DEV, PROD etc). Could you please guide us on how to remove all the entities under and invalid env PRD
thanks bear 1
b
Hey, after delete you might need to run restoreIndecies on the urn: curl -X POST '<http://.../aspects?action=restoreIndices|.../aspects?action=restoreIndices>' --header "Authorization: Bearer ${TKN}" --header 'Content-Type: application/json' --data-raw "{\"urn\":\"$URI\"}"
b
@bulky-electrician-72362 Thank you . can you please advice on how to remove all the entities based on env PRD or if there is an option to invalidate this particular env (PRD) as such , even that would be feasible
@bulky-electrician-72362 Can we have some advice on the above scenario. There are certain entities which got emitted with an invalid env "PRD", which still exist in PROD Datahub. The above solution may work for individual removal. We tried to remove the entities based on a specific env, which is 'PRD' in our case and it shows 0 entities identified even when we have entities in this env. cc: @tall-butcher-30509 @melodic-match-38516
t
@busy-analyst-35820 Let’s try this when we get the PRD clone environment up.