All Products
Search
Document Center

DataWorks:DeleteLineageRelation

Last Updated:Nov 21, 2024

Deletes the lineage between entities. You can call this operation to delete only custom lineages that are registered by users.

Operation description

This operation is in the trial phase. Users who need to call this operation can apply for it. The users can call this operation after the administrator adds the users to the trial list.

Debugging

You can run this interface directly in OpenAPI Explorer, saving you the trouble of calculating signatures. After running successfully, OpenAPI Explorer can automatically generate SDK code samples.

Authorization information

There is currently no authorization information disclosed in the API.

Request parameters

ParameterTypeRequiredDescriptionExample
SrcEntityQualifiedNamestringYes

The unique identifier of the source entity.

maxcompute-table.project.table
DestEntityQualifiedNamestringYes

The unique identifier of the destination entity.

custom-report.report123
RelationshipGuidstringNo

The unique identifier of the lineage.

dfazcdfdfccdedd

Response parameters

ParameterTypeDescriptionExample
object

OpenApiMetaResultModel

HttpStatusCodeinteger

The HTTP status code.

200
ErrorMessagestring

The error message.

qualifiedName should be in format as entity-table.entity-guid
RequestIdstring

The request ID.

64B-587A-8CED-969E1973887FXXX-TT
Successboolean

Indicates whether the request was successful. Valid values:

true

false

true
ErrorCodestring

The error code.

1010040007
Statusboolean

The result of the operation. Valid values:

true: successful

false: failed

true

Examples

Sample success responses

JSONformat

{
  "HttpStatusCode": 200,
  "ErrorMessage": "qualifiedName should be in format as entity-table.entity-guid",
  "RequestId": "64B-587A-8CED-969E1973887FXXX-TT",
  "Success": true,
  "ErrorCode": "1010040007",
  "Status": true
}

Error codes

For a list of error codes, visit the Service error codes.

Change history

Change timeSummary of changesOperation
2024-08-14The request parameters of the API has changedView Change Details