I'm not entirely sure how but I managed to create ...
# troubleshoot
h
I'm not entirely sure how but I managed to create an assertion through the emitter that didn't have a valid URN. When I hit the api to query it, I'm getting failures because of it. I can't delete it through the CLI either because when I tried to query for it, I'm getting no responses. Is there a way to override the API's valid urn assertion so I can figure out what the entity I created was? Or should I just go hit the database directly?
e
Was the urn of the assertion invalid? or the urn of the dataset that the assertion is pointing to invalid? In the first case, it should’ve not ingested anything bc of the urn assertion logic. cc @big-carpet-38439
h
Hmm. I'm wondering if it was the latter. I deleted the dataset through the API hoping it might delete the associated assertion but that didn't fix it either. It might also be an assertion run that was broken and returning the owning assertion is failing. Unfortunately I'm getting an error that doesn't provide further details from the graphql side.
When I try to find it via GMS, I'm getting this in the stacktrace
Copy code
java.net.URISyntaxException: Urn doesn't start with 'urn:'. Urn: searchAcrossEntities at index 0: searchAcrossEntities\n\tat com.linkedin.common.urn.Urn.<init>(Urn.java:80)\n\tat com.linkedin.common.urn.Urn.createFromString(Urn.java:231)\n\tat com.linkedin.metadata.resources.entity.EntityResource.get(EntityResource.java:134)\n\tat sun.reflect.GeneratedMethodAccessor309.invoke(Unknown Source)\n\tat sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)\n\tat java.lang.reflect.Method.invoke(Method.java:498)\n\tat com.linkedin.restli.internal.server.RestLiMethodInvoker.doInvoke(RestLiMethodInvoker.java:177)\n\t... 78 more\n
e
Hmn so it somehow got in but on the get it is causing issues. So @orange-night-91387 added urn validation 14 days ago, so this should not happen any more. i.e. the writes would just fail if any urns in the aspect is not valid
Assuming deleting by urn is also not working, I would suggest directly removing the row from the mysql DB 😞
o
Yeah we didn't add any backfill logic or protection for previously ingested urns 😞 should be protected against this in latest