[ 
https://issues.apache.org/jira/browse/ATLAS-5375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sheetal Shah resolved ATLAS-5375.
---------------------------------
    Fix Version/s: 3.0.0
       Resolution: Fixed

> Fix stale PUT response for /api/atlas/v2/relationship block/unblock 
> propagation
> -------------------------------------------------------------------------------
>
>                 Key: ATLAS-5375
>                 URL: https://issues.apache.org/jira/browse/ATLAS-5375
>             Project: Atlas
>          Issue Type: Improvement
>          Components:  atlas-core
>    Affects Versions: 3.0.0
>            Reporter: Sheetal Shah
>            Assignee: Sheetal Shah
>            Priority: Major
>             Fix For: 3.0.0
>
>          Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> *Summary*
> {{PUT /api/atlas/v2/relationship}} returns HTTP 200 with a stale relationship 
> body. Block/unblock runs in async task 
> {{CLASSIFICATION_PROPAGATION_RELATIONSHIP_UPDATE}} after the response, so the 
> PUT body does not match the request. GET after ~15–30s shows the correct 
> state.
> *Repro (brief)*
>  # Propagate tag on source table via lineage edge.
>  # PUT block with {{blockedPropagatedClassifications: [
> {tag}
> ]}} → wait → verify downstream.
>  # PUT unblock with {{blockedPropagatedClassifications: []}} → PUT body still 
> shows old blocked list; GET after wait is correct.
> *Root cause*
> Response built from graph before deferred task runs; task JSON may have null 
> {{{}propagateTags{}}}.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to