Our Community is getting an upgrade! To get everything ready for the relaunch, we’ll be placing the site in read-only mode starting September 21st.
We really appreciate your understanding while we get things set up behind the scenes. Catch up on all the exciting details about the move here.
Need help or have questions? Drop us a line at [email protected]

Support Questions

Find answers, ask questions, and share your expertise
Announcements
Share your experience with Cloudera on G2 and get a $25 Amazon Gift card.
Hi, I'm CLEO! Something exciting is coming to the Community. Stay Tuned!

Delete custom Type with relationshipAttributeDefs

avatar
Explorer

Hello,

I have built a custom Type with no Entities.  However when I try to delete it I get an error, "Given type InformationAssets has references".  When I pull back that Type using the API I can see it has some built-in relationship:


"relationshipAttributeDefs": [
{
"name": "meanings",
"typeName": "array<AtlasGlossaryTerm>",
"isOptional": true,
"cardinality": "SET",
"valuesMinCount": -1,
"valuesMaxCount": -1,
"isUnique": false,
"isIndexable": false,
"includeInNotification": false,
"searchWeight": -1,
"relationshipTypeName": "AtlasGlossarySemanticAssignment",
"isLegacyAttribute": false
}
]

There are no entities under this Type, so there are no Glossary Terms assigned to it.  I'm not sure how this relationship was created in the first place.  I've deleted relationshipDefs before, but this one "AtlasGlossarySemanticAssignment" appears to be some built-in relationship.  

Does anyone know how I can remove this in order to delete the Type?

Thanks in advance!

1 ACCEPTED SOLUTION

avatar
Explorer

I found out the issue I faced was not because of the relationshipAttributeDefs of "meanings".  This is apparently inherited from the Referenceable supertype.  This was not the cause of me getting the "Given type InformationAssets has references" error when trying to delete.

View solution in original post

1 REPLY 1

avatar
Explorer

I found out the issue I faced was not because of the relationshipAttributeDefs of "meanings".  This is apparently inherited from the Referenceable supertype.  This was not the cause of me getting the "Given type InformationAssets has references" error when trying to delete.