[
https://issues.apache.org/jira/browse/ATLAS-5317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18102532#comment-18102532
]
ASF subversion and git services commented on ATLAS-5317:
--------------------------------------------------------
Commit c1ec5dbb815fd83b13a896bcb43310f977a77652 in atlas's branch
refs/heads/master from sheetalshah1007
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=c1ec5dbb8 ]
ATLAS-5317: Resilient bulk purge with pre-validation, worker batches,… (#704)
* ATLAS-5317: Resilient bulk purge with transactional batching, partial success
handling, and purge audit enhancements
> Make Atlas Purge API more resilient
> -----------------------------------
>
> Key: ATLAS-5317
> URL: https://issues.apache.org/jira/browse/ATLAS-5317
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
> Reporter: Sheetal Shah
> Assignee: Sheetal Shah
> Priority: Major
> Time Spent: 1h
> Remaining Estimate: 0h
>
> h2. Problem Statement
> Atlas exposes a purge API ({{{}PUT /api/atlas/admin/purge{}}}) to hard-delete
> entities. The API accepts a batch of GUIDs but fails the entire request if
> any single entity delete throws an exception. This all-or-nothing behavior
> blocks large clean-up jobs.
> Key issues:
> * One corrupt, missing, or locked GUID causes the entire batch to roll back
> with HTTP 500
> * No structured failure reporting — bad GUIDs are only logged as
> {{{}WARN{}}}; callers cannot identify which GUIDs failed
> * Audit entry stores all input GUIDs in a single row, which can exceed safe
> size limits and cause transaction rollbacks
> * REST purge and background {{PurgeService}} cron can run concurrently on
> the same GUIDs, causing {{PermanentLockingException}}
> * No input validation — non-GUID strings passed to the API cause unexpected
> failures
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
