Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
0.8-incubating
-
None
Description
Background
When multiple requests simultaneously attempt to change the tags associated with an entity, the current implementation might result in APIs returning fewer tags for the entity than is actually associated.
The problem thus causes UI not to behave correctly.
Solution
Implements a synchronization mechanism.
Steps to duplicate the problem:
- Create several tags. Eg. tag1, tag2, tag3, tag4.
- Attach these tags to and entity say ‘testtable1’
- Use the following CURL commands to delete the tags:
curl -X DELETE -u admin:admin 'http://localhost:21000/api/atlas/entities/a2d0b023-aafe-4ddd-bb90-65164af8796c/traits/tag1' -H 'Content-Type: application/json' & curl -X DELETE -u admin:admin 'http://localhost:21000/api/atlas/entities/a2d0b023-aafe-4ddd-bb90-65164af8796c/traits/tag2' -H 'Content-Type: application/json' & curl -X DELETE -u admin:admin 'http://localhost:21000/api/atlas/entities/a2d0b023-aafe-4ddd-bb90-65164af8796c/traits/tag3' -H 'Content-Type: application/json' & curl -X DELETE -u admin:admin 'http://localhost:21000/api/atlas/entities/a2d0b023-aafe-4ddd-bb90-65164af8796c/traits/tag4' -H 'Content-Type: application/json'
You will notice that entity testtable1 ends up with some tags not deleted.
Additional querying with gremlin will show that the edges are deleted correctly.
Attachments
Attachments
Issue Links
- links to