Replies: 2 comments
-
when you ask RACK to look up an ENTITY by identifier, it should find any subclasses with the given identifier. I have confirmed this functionality is working in the test suite. |
Beta Was this translation helpful? Give feedback.
-
The problem here is the way the .yaml file is set up.
Your yaml is set up like this:
And the problem is that a.csv also has some relationships to b1.csv. So any b that is mentioned in a.csv is ingested as an ENTITY. Then when b1.csv rolls around, it is ingested as it's correct type.
so it would be:
NOTE:I also see some duplicates in your first-pass csv files. This isn't causing any error, but should be avoided if possible. PREVENTION:The ingestion nodegroups automatically generated by TA2 are supposed to have "Create if missing" for the main object and "Error if missing" for all the objects connected by properties. This causes an ingestion error to be thrown in this type of situation, preventing the accidental creation of duplicates. The nodegroups you used have all objects "Create if missing," which allows the duplicates to slip through undetected. |
Beta Was this translation helpful? Give feedback.
-
[Moved from the end of a different resolved discussion: 444]
I have a lot ingestion node groups that use Entity for referencing (like polymorphism) . For example Analysis can analyze Requirements, Tests, etc.
However, when I use what you mentioned before. The RACK creates an Entity with the given identifier. Although, there is already a Requirement with the same identifier, which should have been selected.
Should I create multiple node groups that ingest analysis for every type of analyzed element? Or there is a smarter way to do it?
Beta Was this translation helpful? Give feedback.
All reactions