fix(graphql): removed duplicated entity in EntityTypeUrnMapper #12406
+50
−3
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When I tried to create a structured property using the new UI in v0.15.0, I noticed, that it does not work because there is a duplicated entry in the EntityTypeUrnMapper:
Caused by: java.lang.ExceptionInInitializerError: Exception java.lang.IllegalArgumentException: Multiple entries with same key: dataProcessInstance=urn:li:entityType:datahub.dataProcessInstance and dataProcessInstance=urn:li:entityType:datahub.dataProcessInstance [in thread "ForkJoinPool.commonPool-worker-325"]
The duplicated entry was added with #12263.
I have also added some simple tests of EntityTypeUrnMapperTest (and EntityTypeMapperTest) to make sure that duplicated entries will be noticed in the future there. I have not tested the tests locally, we will see whether they work in the CI pipeline.
Checklist