Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Multiple entities of the same type with the same qualified name are created in atlas #592

Closed
ruxandraRosu opened this issue Jan 22, 2019 · 9 comments
Milestone

Comments

@ruxandraRosu
Copy link
Contributor

Multiple entities are created in atlas repository with the same qualifiedName. The qualifiedName should be unique for an entity type

@cmgrote
Copy link
Member

cmgrote commented Jan 22, 2019

Agreed: did you have some example payloads to illustrate the duplication? @grahamwallis ^^

@ruxandraRosu
Copy link
Contributor Author

ruxandraRosu commented Jan 22, 2019

entities_with_same_qualified_name.txt
The creation is done through enterpriseConnector - so through REST calls. I've masked the host name, but the value is the same

@cmgrote
Copy link
Member

cmgrote commented Jan 22, 2019

Hmm, makes it difficult to see where the duplicate name is originating in the first place... Does this duplicate qualifiedName appear to be originating from Atlas, or from IGC?

@grahamwallis
Copy link
Contributor

The connector defines the qualifiedName attribute in Atlas as being unique, but It looks to me as if the only place that isUnique actually has an effect is during index creation. We could police uniqueness at various levels, one of which would be the metadataCollection - but I am not sure whether that would have too much of a performance impact.

It certainly seems that two entities are being created for the same SoftwareServer, which is a problem in itself. But it is possible that we should be policing uniqueness of values at the receiving repository as well.

@cmgrote cmgrote added this to the Think 2019 milestone Jan 22, 2019
@ruxandraRosu
Copy link
Contributor Author

Hi,
These entities are created by IV OMAS through the enterprise connector, meaning that REST calls are issued to both atlas and igc-repo-proxy. Regarding the comment above, there were some WARN messages in atlas about not being able to create the index because OM_Referenceable has too many subtypes. Could this be linked?

@grahamwallis
Copy link
Contributor

I doubt that the warning is related - the fundamental issue seems to be that the same software server is being created as two different entities (different GUIDs). Do we know why that is causing the duplication? Should the enterprise connector actually decide on a (single) home repository and create the entity there?
@mandy-chessell ^^

@cmgrote
Copy link
Member

cmgrote commented Apr 16, 2019

Just checking if this is still a problem to be resolved (given the age of the issue it seems potentially stale)?

@planetf1
Copy link
Member

I think this is defunct now given we are moving away from the atlas fork?

@cmgrote
Copy link
Member

cmgrote commented Oct 17, 2019

Closing as stale given move away from Atlas fork and lack of updates over past 6 months. Please open a new issue on the specific problem related to latest configs (ie. not including Atlas fork), if there is an issue still remaining to be addressed.

@cmgrote cmgrote closed this as completed Oct 17, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants