Hi, i just found the interesting error(?) regarding deleting entities.. 1. when i delete entities via

datahub delete --urn <some_urn>

, the path/button to the entity also get deleted. 2. However, when i delete entities using

DELETE FROM ~

on datahub database (metadata_aspect_v2), the path/button to the entity does not get deleted !! (Although there's no related data in DB) 3. After that, even if i try

datahub delete --urn <some_urn>

on the same entity, the path/button does not get deleted. (At this point, somehow it's impossible to hide this path/buttons?...) Does anyone know about this issue or how to solve this problem? 🙂

That's because the data still persists in ES

@better-orange-49102 Wow, thanks for the clear answer.!!! 🙂 I'll try both ways and update this thread. Thank you again !

When deleting data you have to use the CLI so it cleans both RDBMS and elasticsearch. If you have done the deletion of mysql only then you can run the commands given here to re-index elasticsearch https://datahubproject.io/docs/how/restore-indices Make sure to use the

-a clean

as mentioned in the docs to clean up entries no longer present in RDBMS

I checked the job config, and all the DB connection info & secrets are fine. Heres' my log on restoring job :

Executing Step 4/4: SendMAEStep...
Sending MAE from local DB...
Found 6487 latest aspects in aspects table
Reading rows 0 through 1000 from the aspects table.
Caught exception during attempt 0 of Step with id SendMAEStep: java.util.UnknownFormatConversionException: Conversion = 'D'

This is really strange. The DB is working fine otherwise? I'm not sure we've had anyone using CloudSQL before

• I created something like cloud-secret instead of mysql-secret. (all the values are properly replaced on helm chart) • i deployed with helm chart - and no previous issues 🙂

This should not be due to CloudSQL. I have done this restore job multiple times and we are also using GCP's CloudSQL. No error ever happened for us and the job was successful.