Hi folks, i tried to use datahub cli in order to d...
# troubleshoot
f
Hi folks, i tried to use datahub cli in order to delete all the metadata.
🧵 1
This is the comanda
Copy code
datahub delete  --entity_type dataset --env PROD --hard
i have 471 objecte
Copy code
this will delete 471 entities. Are you sure? [y/N]: y
but the datahub dosent delete them
Copy code
Took 74.657 seconds to hard delete 0 rows for 471 entitie
Do you have any ideea? Thx 😄
b
@incalculable-ocean-74010 Do you mind advising on this ? When you visit DataHub you still see all of those entities?
f
yep, i see them in the ui. The fun fact is that i had over 10k datasets, and most of them are deleted (only those 471 remains)
i
Hello Dragos, This is a strange behaviour, I’ve seen it happen when the entities no longer exist in the relational database but still exist in elasticsearch indices because not all delete MCPs have yet to be processed. Could you access your relational DB and confirm whether those entities still exist or not?
f
Hi pedro, yep, there are not in the db but they are still cahched in elastich search i think. I runned datahub-datahub-restore-indices-job-template but i still have the in Recently Viewed/Most Popular
i
Dragos, do those 471 entities remain in the UI or only in the recently Viewed? I.e: if you search for them in the search tab do they appear?
f
nop , i dont find them in search
i
Ok, this is good, it means the entities are no longer in search indicies. The reason why datasets might have appeared in the recently viewed/most popular is because of caching. It should go away with a hard refresh of the browser.
cc @big-carpet-38439
b
Yeah it will take some time to clear the cache (~10m) but I'm not sure why you had to run reindexing