[
https://issues.apache.org/jira/browse/ATLAS-4988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18050849#comment-18050849
]
Umesh Patil edited comment on ATLAS-4988 at 5/8/26 9:49 AM:
------------------------------------------------------------
*API Usage Note: force on typedef delete (ATLAS-4988)*
*Supported Endpoints*
*Bulk delete*
DELETE /api/atlas/v2/types/typedefs?force=true|false
*Delete by name*
DELETE /api/atlas/v2/types/typedef/name/\{typeName}?force=true|false
force is optional and defaults to false.
*Important: force only affects Business Metadata typedefs*
The force parameter is meaningful only for deleting Business Metadata
(businessMetadataDefs) typedefs.
When deleting a Business Metadata type:
force=false (default)
Performs the standard pre-delete reference validation.
If the BM is still assigned to entities, deletion fails with reference-related
errors.
force=true
Skips the pre-delete reference validation and deletes the Business Metadata
typedef even if references still exist.
This may leave orphaned BM values on entities.
*Non-Business Metadata typedefs*
For all other typedef categories (enum, struct, classification, entity,
relationship, etc.), the force parameter does not bypass existing validation or
reference checks.
Behavior for these typedefs remains unchanged from previous releases:
Types without references can still be deleted successfully.
Types with existing references or instances continue to fail with errors such
as:
409 / TYPE_HAS_REFERENCES
This behavior is consistent regardless of whether force=true or force=false is
supplied.
was (Author: JIRAUSER311456):
Please Refer above Attachment (JIRA-4988 TestCases Doc) to see what all
scenarios are covered while testing JIRA-4988, also covered comparison in BM
Deletion Time between old and updated code.
> BusinessMetadata with attribute of data type Array takes time to Delete.
> ------------------------------------------------------------------------
>
> Key: ATLAS-4988
> URL: https://issues.apache.org/jira/browse/ATLAS-4988
> Project: Atlas
> Issue Type: Improvement
> Components: atlas-core
> Affects Versions: 3.0.0, 2.4.0
> Reporter: chaitali borole
> Assignee: Umesh Patil
> Priority: Major
> Time Spent: 2h 20m
> Remaining Estimate: 0h
>
> whenever we use a multi valued attribute i.e array data type for an attribute.
> 1.When such BM is not assigned to any entities and you try to delete it even
> then It tries to fetch all the entities under the respective applicable type
> name
> and finally deletes the BM when it doesn't find the BM-attribute assigned to
> any of entities.
> array type is not indexed in solr hence the above issue.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
