sheetalshah1007 opened a new pull request, #749: URL: https://github.com/apache/atlas/pull/749
## What changes were proposed in this pull request? Follow-up to ATLAS-5375 ([#729](https://github.com/apache/atlas/pull/729)). If the blocked list on a relationship was **empty** and a client blocked a tag, the graph was updated correctly — but the **PUT response** could still show the old edge (tag propagated, nothing blocked). **GET** right after PUT showed the right state. This patch fixes that PUT response for **empty → blocked** (first block and block after unblock): - Write the blocked list with remove-then-set (copy-on-write) - Read it back with getListProperty, matching how it is written - Reload the relationship edge before building the PUT body Entity tag updates still run in the background; no API change. ## How was this patch tested? - Tested the scenario manually on running Atlas server - Additionally, added a test which checks that blocking from an empty list updates PUT and GET before the background task finishes. Existing unblock tests still pass. `mvn -pl repository -Dtest=ClassificationPropagationWithTasksTest,ClassificationPropagationTasksTest,ClassificationTaskTest,ClassificationPropagateTaskFactoryTest test` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
