Entity Class

Initializes a new instance of Entity for mocking.

The HTTP pipeline for sending and receiving REST requests and responses.

Associate a classification to multiple entities in bulk.

[Protocol Method] Associate a classification to multiple entities in bulk.

• This protocol method allows explicit creation of the request and processing of the response for advanced scenarios.
• Please try the simpler AddClassification(ClassificationAssociateConfig, CancellationToken) convenience overload with strongly typed models first.

Associate a classification to multiple entities in bulk.

[Protocol Method] Associate a classification to multiple entities in bulk.

• This protocol method allows explicit creation of the request and processing of the response for advanced scenarios.
• Please try the simpler AddClassificationAsync(ClassificationAssociateConfig, CancellationToken) convenience overload with strongly typed models first.

Add classifications to an existing entity represented by a GUID.

[Protocol Method] Add classifications to an existing entity represented by a GUID.

• This protocol method allows explicit creation of the request and processing of the response for advanced scenarios.
• Please try the simpler AddClassifications(String, IEnumerable<AtlasClassification>, CancellationToken) convenience overload with strongly typed models first.

Add classifications to an existing entity represented by a GUID.

[Protocol Method] Add classifications to an existing entity represented by a GUID.

• This protocol method allows explicit creation of the request and processing of the response for advanced scenarios.
• Please try the simpler AddClassificationsAsync(String, IEnumerable<AtlasClassification>, CancellationToken) convenience overload with strongly typed models first.

Add classification to the entity identified by its type and unique attributes.

[Protocol Method] Add classification to the entity identified by its type and unique attributes.

• This protocol method allows explicit creation of the request and processing of the response for advanced scenarios.
• Please try the simpler AddClassificationsByUniqueAttribute(String, IEnumerable<AtlasClassification>, String, CancellationToken) convenience overload with strongly typed models first.

Add classification to the entity identified by its type and unique attributes.

[Protocol Method] Add classification to the entity identified by its type and unique attributes.

• This protocol method allows explicit creation of the request and processing of the response for advanced scenarios.
• Please try the simpler AddClassificationsByUniqueAttributeAsync(String, IEnumerable<AtlasClassification>, String, CancellationToken) convenience overload with strongly typed models first.

Add given labels to a given entity.

[Protocol Method] Add given labels to a given entity.

• This protocol method allows explicit creation of the request and processing of the response for advanced scenarios.
• Please try the simpler AddLabel(String, IEnumerable<String>, CancellationToken) convenience overload with strongly typed models first.

Add given labels to a given entity.

[Protocol Method] Add given labels to a given entity.

• This protocol method allows explicit creation of the request and processing of the response for advanced scenarios.
• Please try the simpler AddLabelAsync(String, IEnumerable<String>, CancellationToken) convenience overload with strongly typed models first.

Add given labels to a given entity identified by its type and unique attributes.

If labels is null/empty, no labels will be added.

In addition to the typeName path parameter, attribute key-value pair(s) can be provided in the following format: attr:<attrName>=<attrValue>.

NOTE: The attrName and attrValue should be unique across entities, eg. qualifiedName.

The REST request would look something like this: PUT /v2/entity/uniqueAttribute/type/aType?attr:aTypeAttribute=someValue.

[Protocol Method] Add given labels to a given entity identified by its type and unique attributes.

If labels is null/empty, no labels will be added.

In addition to the typeName path parameter, attribute key-value pair(s) can be provided in the following format: attr:<attrName>=<attrValue>.

NOTE: The attrName and attrValue should be unique across entities, eg. qualifiedName.

The REST request would look something like this: PUT /v2/entity/uniqueAttribute/type/aType?attr:aTypeAttribute=someValue.

• This protocol method allows explicit creation of the request and processing of the response for advanced scenarios.
• Please try the simpler AddLabelsByUniqueAttribute(String, IEnumerable<String>, String, CancellationToken) convenience overload with strongly typed models first.

Add given labels to a given entity identified by its type and unique attributes.

If labels is null/empty, no labels will be added.

In addition to the typeName path parameter, attribute key-value pair(s) can be provided in the following format: attr:<attrName>=<attrValue>.

NOTE: The attrName and attrValue should be unique across entities, eg. qualifiedName.

The REST request would look something like this: PUT /v2/entity/uniqueAttribute/type/aType?attr:aTypeAttribute=someValue.

[Protocol Method] Add given labels to a given entity identified by its type and unique attributes.

If labels is null/empty, no labels will be added.

In addition to the typeName path parameter, attribute key-value pair(s) can be provided in the following format: attr:<attrName>=<attrValue>.

NOTE: The attrName and attrValue should be unique across entities, eg. qualifiedName.

The REST request would look something like this: PUT /v2/entity/uniqueAttribute/type/aType?attr:aTypeAttribute=someValue.

• This protocol method allows explicit creation of the request and processing of the response for advanced scenarios.
• Please try the simpler AddLabelsByUniqueAttributeAsync(String, IEnumerable<String>, String, CancellationToken) convenience overload with strongly typed models first.

Add business metadata to an entity.

[Protocol Method] Add business metadata to an entity.

• This protocol method allows explicit creation of the request and processing of the response for advanced scenarios.
• Please try the simpler AddOrUpdateBusinessMetadata(String, IDictionary<String,IDictionary<String,BinaryData>>, Nullable<Boolean>, CancellationToken) convenience overload with strongly typed models first.

Add business metadata to an entity.

[Protocol Method] Add business metadata to an entity.

• This protocol method allows explicit creation of the request and processing of the response for advanced scenarios.
• Please try the simpler AddOrUpdateBusinessMetadataAsync(String, IDictionary<String,IDictionary<String,BinaryData>>, Nullable<Boolean>, CancellationToken) convenience overload with strongly typed models first.

Add or update business metadata attributes.

[Protocol Method] Add or update business metadata attributes.

• This protocol method allows explicit creation of the request and processing of the response for advanced scenarios.
• Please try the simpler AddOrUpdateBusinessMetadataAttributes(String, String, IDictionary<String,BinaryData>, CancellationToken) convenience overload with strongly typed models first.

Add or update business metadata attributes.

[Protocol Method] Add or update business metadata attributes.

• This protocol method allows explicit creation of the request and processing of the response for advanced scenarios.
• Please try the simpler AddOrUpdateBusinessMetadataAttributesAsync(String, String, IDictionary<String,BinaryData>, CancellationToken) convenience overload with strongly typed models first.

Create or update entities in bulk. Existing entity is matched using its unique guid if supplied or by its unique attributes eg: qualifiedName. Map and array of collections are not well supported. E.g., array<array<int>>, array<map<string, int>>. For each contact type, the maximum number of contacts is 20.

[Protocol Method] Create or update entities in bulk. Existing entity is matched using its unique guid if supplied or by its unique attributes eg: qualifiedName. Map and array of collections are not well supported. E.g., array<array<int>>, array<map<string, int>>. For each contact type, the maximum number of contacts is 20.

• This protocol method allows explicit creation of the request and processing of the response for advanced scenarios.
• Please try the simpler BatchCreateOrUpdate(AtlasEntitiesWithExtInfo, String, Nullable<BusinessAttributeUpdateBehavior>, CancellationToken) convenience overload with strongly typed models first.

Create or update entities in bulk. Existing entity is matched using its unique guid if supplied or by its unique attributes eg: qualifiedName. Map and array of collections are not well supported. E.g., array<array<int>>, array<map<string, int>>. For each contact type, the maximum number of contacts is 20.

[Protocol Method] Create or update entities in bulk. Existing entity is matched using its unique guid if supplied or by its unique attributes eg: qualifiedName. Map and array of collections are not well supported. E.g., array<array<int>>, array<map<string, int>>. For each contact type, the maximum number of contacts is 20.

• This protocol method allows explicit creation of the request and processing of the response for advanced scenarios.
• Please try the simpler BatchCreateOrUpdateAsync(AtlasEntitiesWithExtInfo, String, Nullable<BusinessAttributeUpdateBehavior>, CancellationToken) convenience overload with strongly typed models first.

Delete a list of entities in bulk identified by their GUIDs or unique attributes.

[Protocol Method] Delete a list of entities in bulk identified by their GUIDs or unique attributes.

• This protocol method allows explicit creation of the request and processing of the response for advanced scenarios.
• Please try the simpler BatchDelete(IEnumerable<String>, CancellationToken) convenience overload with strongly typed models first.

Delete a list of entities in bulk identified by their GUIDs or unique attributes.

[Protocol Method] Delete a list of entities in bulk identified by their GUIDs or unique attributes.

• This protocol method allows explicit creation of the request and processing of the response for advanced scenarios.
• Please try the simpler BatchDeleteAsync(IEnumerable<String>, CancellationToken) convenience overload with strongly typed models first.

Bulk API to retrieve list of entities identified by its unique attributes. In addition to the typeName path parameter, attribute key-value pair(s) can be provided in the following format

typeName=&lt;typeName>&attr_1:&lt;attrName>=&lt;attrValue>&attr_2:&lt;attrName>=&lt;attrValue>&attr_3:&lt;attrName>=&lt;attrValue>

NOTE: The attrName should be an unique attribute for the given entity-type. The REST request would look something like this

GET /v2/entity/bulk/uniqueAttribute/type/hive_db?attr_1:qualifiedName=db1@cl1&attr_2:qualifiedName=db2@cl1

Note: at least one unique attribute must be provided.

[Protocol Method] Bulk API to retrieve list of entities identified by its unique attributes. In addition to the typeName path parameter, attribute key-value pair(s) can be provided in the following format

typeName=&lt;typeName>&attr_1:&lt;attrName>=&lt;attrValue>&attr_2:&lt;attrName>=&lt;attrValue>&attr_3:&lt;attrName>=&lt;attrValue>

NOTE: The attrName should be an unique attribute for the given entity-type. The REST request would look something like this

GET /v2/entity/bulk/uniqueAttribute/type/hive_db?attr_1:qualifiedName=db1@cl1&attr_2:qualifiedName=db2@cl1

Note: at least one unique attribute must be provided.

• This protocol method allows explicit creation of the request and processing of the response for advanced scenarios.
• Please try the simpler BatchGetByUniqueAttributes(String, Nullable<Boolean>, Nullable<Boolean>, String, CancellationToken) convenience overload with strongly typed models first.

Bulk API to retrieve list of entities identified by its unique attributes. In addition to the typeName path parameter, attribute key-value pair(s) can be provided in the following format

typeName=&lt;typeName>&attr_1:&lt;attrName>=&lt;attrValue>&attr_2:&lt;attrName>=&lt;attrValue>&attr_3:&lt;attrName>=&lt;attrValue>

NOTE: The attrName should be an unique attribute for the given entity-type. The REST request would look something like this

GET /v2/entity/bulk/uniqueAttribute/type/hive_db?attr_1:qualifiedName=db1@cl1&attr_2:qualifiedName=db2@cl1

Note: at least one unique attribute must be provided.

[Protocol Method] Bulk API to retrieve list of entities identified by its unique attributes. In addition to the typeName path parameter, attribute key-value pair(s) can be provided in the following format

typeName=&lt;typeName>&attr_1:&lt;attrName>=&lt;attrValue>&attr_2:&lt;attrName>=&lt;attrValue>&attr_3:&lt;attrName>=&lt;attrValue>

NOTE: The attrName should be an unique attribute for the given entity-type. The REST request would look something like this

GET /v2/entity/bulk/uniqueAttribute/type/hive_db?attr_1:qualifiedName=db1@cl1&attr_2:qualifiedName=db2@cl1

Note: at least one unique attribute must be provided.

• This protocol method allows explicit creation of the request and processing of the response for advanced scenarios.
• Please try the simpler BatchGetByUniqueAttributesAsync(String, Nullable<Boolean>, Nullable<Boolean>, String, CancellationToken) convenience overload with strongly typed models first.

Set classifications on entities in bulk.

[Protocol Method] Set classifications on entities in bulk.

• This protocol method allows explicit creation of the request and processing of the response for advanced scenarios.
• Please try the simpler BatchSetClassifications(AtlasEntityHeaders, CancellationToken) convenience overload with strongly typed models first.

Set classifications on entities in bulk.

[Protocol Method] Set classifications on entities in bulk.

• This protocol method allows explicit creation of the request and processing of the response for advanced scenarios.
• Please try the simpler BatchSetClassificationsAsync(AtlasEntityHeaders, CancellationToken) convenience overload with strongly typed models first.

Create or update an entity. Existing entity is matched using its unique guid if supplied or by its unique attributes eg: qualifiedName. Map and array of collections are not well supported. E.g., array<array<int>>, array<map<string, int>>. For each contact type, the maximum number of contacts is 20.

[Protocol Method] Create or update an entity. Existing entity is matched using its unique guid if supplied or by its unique attributes eg: qualifiedName. Map and array of collections are not well supported. E.g., array<array<int>>, array<map<string, int>>. For each contact type, the maximum number of contacts is 20.

• This protocol method allows explicit creation of the request and processing of the response for advanced scenarios.
• Please try the simpler CreateOrUpdate(AtlasEntityWithExtInfo, Nullable<BusinessAttributeUpdateBehavior>, String, CancellationToken) convenience overload with strongly typed models first.

Create or update an entity. Existing entity is matched using its unique guid if supplied or by its unique attributes eg: qualifiedName. Map and array of collections are not well supported. E.g., array<array<int>>, array<map<string, int>>. For each contact type, the maximum number of contacts is 20.

[Protocol Method] Create or update an entity. Existing entity is matched using its unique guid if supplied or by its unique attributes eg: qualifiedName. Map and array of collections are not well supported. E.g., array<array<int>>, array<map<string, int>>. For each contact type, the maximum number of contacts is 20.

• This protocol method allows explicit creation of the request and processing of the response for advanced scenarios.
• Please try the simpler CreateOrUpdateAsync(AtlasEntityWithExtInfo, Nullable<BusinessAttributeUpdateBehavior>, String, CancellationToken) convenience overload with strongly typed models first.

Delete an entity identified by its GUID.

[Protocol Method] Delete an entity identified by its GUID.

• This protocol method allows explicit creation of the request and processing of the response for advanced scenarios.
• Please try the simpler Delete(String, CancellationToken) convenience overload with strongly typed models first.

Delete an entity identified by its GUID.

[Protocol Method] Delete an entity identified by its GUID.

• This protocol method allows explicit creation of the request and processing of the response for advanced scenarios.
• Please try the simpler DeleteAsync(String, CancellationToken) convenience overload with strongly typed models first.

Delete an entity identified by its type and unique attributes. In addition to the typeName path parameter, attribute key-value pair(s) can be provided in the following format: attr:&lt;attrName>=&lt;attrValue>. NOTE: The attrName and attrValue should be unique across entities, eg. qualifiedName.

The REST request would look something like this: DELETE /v2/entity/uniqueAttribute/type/aType?attr:aTypeAttribute=someValue.

[Protocol Method] Delete an entity identified by its type and unique attributes. In addition to the typeName path parameter, attribute key-value pair(s) can be provided in the following format: attr:&lt;attrName>=&lt;attrValue>. NOTE: The attrName and attrValue should be unique across entities, eg. qualifiedName.

The REST request would look something like this: DELETE /v2/entity/uniqueAttribute/type/aType?attr:aTypeAttribute=someValue.

• This protocol method allows explicit creation of the request and processing of the response for advanced scenarios.
• Please try the simpler DeleteByUniqueAttribute(String, String, CancellationToken) convenience overload with strongly typed models first.

Delete an entity identified by its type and unique attributes. In addition to the typeName path parameter, attribute key-value pair(s) can be provided in the following format: attr:&lt;attrName>=&lt;attrValue>. NOTE: The attrName and attrValue should be unique across entities, eg. qualifiedName.

The REST request would look something like this: DELETE /v2/entity/uniqueAttribute/type/aType?attr:aTypeAttribute=someValue.

[Protocol Method] Delete an entity identified by its type and unique attributes. In addition to the typeName path parameter, attribute key-value pair(s) can be provided in the following format: attr:&lt;attrName>=&lt;attrValue>. NOTE: The attrName and attrValue should be unique across entities, eg. qualifiedName.

The REST request would look something like this: DELETE /v2/entity/uniqueAttribute/type/aType?attr:aTypeAttribute=someValue.

• This protocol method allows explicit creation of the request and processing of the response for advanced scenarios.
• Please try the simpler DeleteByUniqueAttributeAsync(String, String, CancellationToken) convenience overload with strongly typed models first.

Get the sample Template for uploading/creating bulk BusinessMetaData.

[Protocol Method] Get the sample Template for uploading/creating bulk BusinessMetaData

• This protocol method allows explicit creation of the request and processing of the response for advanced scenarios.
• Please try the simpler GetBusinessMetadataTemplate(CancellationToken) convenience overload with strongly typed models first.

Get the sample Template for uploading/creating bulk BusinessMetaData.

[Protocol Method] Get the sample Template for uploading/creating bulk BusinessMetaData

• This protocol method allows explicit creation of the request and processing of the response for advanced scenarios.
• Please try the simpler GetBusinessMetadataTemplateAsync(CancellationToken) convenience overload with strongly typed models first.

List entities in bulk identified by its GUIDs.

[Protocol Method] List entities in bulk identified by its GUIDs.

• This protocol method allows explicit creation of the request and processing of the response for advanced scenarios.
• Please try the simpler GetByIds(IEnumerable<String>, Nullable<Boolean>, Nullable<Boolean>, CancellationToken) convenience overload with strongly typed models first.

List entities in bulk identified by its GUIDs.

[Protocol Method] List entities in bulk identified by its GUIDs.

• This protocol method allows explicit creation of the request and processing of the response for advanced scenarios.
• Please try the simpler GetByIdsAsync(IEnumerable<String>, Nullable<Boolean>, Nullable<Boolean>, CancellationToken) convenience overload with strongly typed models first.

Get complete definition of an entity given its type and unique attribute.

In addition to the typeName path parameter, attribute key-value pair(s) can be provided in the following format: attr:&lt;attrName>=<attrValue>.

NOTE: The attrName and attrValue should be unique across entities, eg. qualifiedName.

The REST request would look something like this: GET /v2/entity/uniqueAttribute/type/aType?attr:aTypeAttribute=someValue.

[Protocol Method] Get complete definition of an entity given its type and unique attribute.

In addition to the typeName path parameter, attribute key-value pair(s) can be provided in the following format: attr:&lt;attrName>=<attrValue>.

NOTE: The attrName and attrValue should be unique across entities, eg. qualifiedName.

The REST request would look something like this: GET /v2/entity/uniqueAttribute/type/aType?attr:aTypeAttribute=someValue.

• This protocol method allows explicit creation of the request and processing of the response for advanced scenarios.
• Please try the simpler GetByUniqueAttribute(String, Nullable<Boolean>, Nullable<Boolean>, String, CancellationToken) convenience overload with strongly typed models first.

Get complete definition of an entity given its type and unique attribute.

In addition to the typeName path parameter, attribute key-value pair(s) can be provided in the following format: attr:&lt;attrName>=<attrValue>.

NOTE: The attrName and attrValue should be unique across entities, eg. qualifiedName.

The REST request would look something like this: GET /v2/entity/uniqueAttribute/type/aType?attr:aTypeAttribute=someValue.

[Protocol Method] Get complete definition of an entity given its type and unique attribute.

In addition to the typeName path parameter, attribute key-value pair(s) can be provided in the following format: attr:&lt;attrName>=<attrValue>.

NOTE: The attrName and attrValue should be unique across entities, eg. qualifiedName.

The REST request would look something like this: GET /v2/entity/uniqueAttribute/type/aType?attr:aTypeAttribute=someValue.

• This protocol method allows explicit creation of the request and processing of the response for advanced scenarios.
• Please try the simpler GetByUniqueAttributeAsync(String, Nullable<Boolean>, Nullable<Boolean>, String, CancellationToken) convenience overload with strongly typed models first.

Get classification for a given entity represented by a GUID.

[Protocol Method] Get classification for a given entity represented by a GUID.

• This protocol method allows explicit creation of the request and processing of the response for advanced scenarios.
• Please try the simpler GetClassification(String, String, CancellationToken) convenience overload with strongly typed models first.

Get classification for a given entity represented by a GUID.

[Protocol Method] Get classification for a given entity represented by a GUID.

• This protocol method allows explicit creation of the request and processing of the response for advanced scenarios.
• Please try the simpler GetClassificationAsync(String, String, CancellationToken) convenience overload with strongly typed models first.

List classifications for a given entity represented by a GUID.

[Protocol Method] List classifications for a given entity represented by a GUID.

• This protocol method allows explicit creation of the request and processing of the response for advanced scenarios.
• Please try the simpler GetClassifications(String, CancellationToken) convenience overload with strongly typed models first.

List classifications for a given entity represented by a GUID.

[Protocol Method] List classifications for a given entity represented by a GUID.

• This protocol method allows explicit creation of the request and processing of the response for advanced scenarios.
• Please try the simpler GetClassificationsAsync(String, CancellationToken) convenience overload with strongly typed models first.

Get complete definition of an entity given its GUID.

[Protocol Method] Get complete definition of an entity given its GUID.

• This protocol method allows explicit creation of the request and processing of the response for advanced scenarios.
• Please try the simpler GetEntity(String, Nullable<Boolean>, Nullable<Boolean>, CancellationToken) convenience overload with strongly typed models first.

Get complete definition of an entity given its GUID.

[Protocol Method] Get complete definition of an entity given its GUID.

• This protocol method allows explicit creation of the request and processing of the response for advanced scenarios.
• Please try the simpler GetEntityAsync(String, Nullable<Boolean>, Nullable<Boolean>, CancellationToken) convenience overload with strongly typed models first.

Get entity header given its GUID.

[Protocol Method] Get entity header given its GUID.

• This protocol method allows explicit creation of the request and processing of the response for advanced scenarios.
• Please try the simpler GetHeader(String, CancellationToken) convenience overload with strongly typed models first.

Get entity header given its GUID.

[Protocol Method] Get entity header given its GUID.

• This protocol method allows explicit creation of the request and processing of the response for advanced scenarios.
• Please try the simpler GetHeaderAsync(String, CancellationToken) convenience overload with strongly typed models first.

Upload the file for creating Business Metadata in BULK.

Upload the file for creating Business Metadata in BULK.

[Protocol Method] Upload the file for creating Business Metadata in BULK

• This protocol method allows explicit creation of the request and processing of the response for advanced scenarios.
• Please try the simpler ImportBusinessMetadata(BusinessMetadataOptions, CancellationToken) convenience overload with strongly typed models first.

Upload the file for creating Business Metadata in BULK.

[Protocol Method] Upload the file for creating Business Metadata in BULK

• This protocol method allows explicit creation of the request and processing of the response for advanced scenarios.
• Please try the simpler ImportBusinessMetadataAsync(BusinessMetadataOptions, CancellationToken) convenience overload with strongly typed models first.

Move existing entities to the target collection.

[Protocol Method] Move existing entities to the target collection.

• This protocol method allows explicit creation of the request and processing of the response for advanced scenarios.
• Please try the simpler MoveEntitiesToCollection(String, MoveEntitiesConfig, CancellationToken) convenience overload with strongly typed models first.

Move existing entities to the target collection.

[Protocol Method] Move existing entities to the target collection.

• This protocol method allows explicit creation of the request and processing of the response for advanced scenarios.
• Please try the simpler MoveEntitiesToCollectionAsync(String, MoveEntitiesConfig, CancellationToken) convenience overload with strongly typed models first.

Remove business metadata from an entity.

[Protocol Method] Remove business metadata from an entity.

• This protocol method allows explicit creation of the request and processing of the response for advanced scenarios.
• Please try the simpler RemoveBusinessMetadata(String, IDictionary<String,IDictionary<String,BinaryData>>, CancellationToken) convenience overload with strongly typed models first.

Remove business metadata from an entity.

[Protocol Method] Remove business metadata from an entity.

• This protocol method allows explicit creation of the request and processing of the response for advanced scenarios.
• Please try the simpler RemoveBusinessMetadataAsync(String, IDictionary<String,IDictionary<String,BinaryData>>, CancellationToken) convenience overload with strongly typed models first.

Delete business metadata attributes from an entity.

[Protocol Method] Delete business metadata attributes from an entity.

• This protocol method allows explicit creation of the request and processing of the response for advanced scenarios.
• Please try the simpler RemoveBusinessMetadataAttributes(String, String, IDictionary<String,BinaryData>, CancellationToken) convenience overload with strongly typed models first.

Delete business metadata attributes from an entity.

[Protocol Method] Delete business metadata attributes from an entity.

• This protocol method allows explicit creation of the request and processing of the response for advanced scenarios.
• Please try the simpler RemoveBusinessMetadataAttributesAsync(String, String, IDictionary<String,BinaryData>, CancellationToken) convenience overload with strongly typed models first.

[Protocol Method] Delete a given classification from an existing entity represented by a GUID.

• This protocol method allows explicit creation of the request and processing of the response for advanced scenarios.

[Protocol Method] Delete a given classification from an existing entity represented by a GUID.

• This protocol method allows explicit creation of the request and processing of the response for advanced scenarios.

[Protocol Method] Delete a given classification from an entity identified by its type and unique attributes.

• This protocol method allows explicit creation of the request and processing of the response for advanced scenarios.

[Protocol Method] Delete a given classification from an entity identified by its type and unique attributes.

• This protocol method allows explicit creation of the request and processing of the response for advanced scenarios.

Delete given labels to a given entity.

[Protocol Method] Delete given labels to a given entity.

• This protocol method allows explicit creation of the request and processing of the response for advanced scenarios.
• Please try the simpler RemoveLabels(String, IEnumerable<String>, CancellationToken) convenience overload with strongly typed models first.

Delete given labels to a given entity.

[Protocol Method] Delete given labels to a given entity.

• This protocol method allows explicit creation of the request and processing of the response for advanced scenarios.
• Please try the simpler RemoveLabelsAsync(String, IEnumerable<String>, CancellationToken) convenience overload with strongly typed models first.

Delete given labels to a given entity identified by its type and unique attribute.

If labels is null/empty, no labels will be removed.

If any labels in labels set are non-existing labels, they will be ignored, only existing labels will be removed. In addition to the typeName path parameter, attribute key-value pair(s) can be provided in the following format: attr:<attrName>=<attrValue>. NOTE: The attrName and attrValue should be unique across entities, eg. qualifiedName. The REST request would look something like this: DELETE /v2/entity/uniqueAttribute/type/aType?attr:aTypeAttribute=someValue.

[Protocol Method] Delete given labels to a given entity identified by its type and unique attribute.

If labels is null/empty, no labels will be removed.

If any labels in labels set are non-existing labels, they will be ignored, only existing labels will be removed. In addition to the typeName path parameter, attribute key-value pair(s) can be provided in the following format: attr:<attrName>=<attrValue>. NOTE: The attrName and attrValue should be unique across entities, eg. qualifiedName. The REST request would look something like this: DELETE /v2/entity/uniqueAttribute/type/aType?attr:aTypeAttribute=someValue.

• This protocol method allows explicit creation of the request and processing of the response for advanced scenarios.
• Please try the simpler RemoveLabelsByUniqueAttribute(String, IEnumerable<String>, String, CancellationToken) convenience overload with strongly typed models first.

Delete given labels to a given entity identified by its type and unique attribute.

If labels is null/empty, no labels will be removed.

If any labels in labels set are non-existing labels, they will be ignored, only existing labels will be removed. In addition to the typeName path parameter, attribute key-value pair(s) can be provided in the following format: attr:<attrName>=<attrValue>. NOTE: The attrName and attrValue should be unique across entities, eg. qualifiedName. The REST request would look something like this: DELETE /v2/entity/uniqueAttribute/type/aType?attr:aTypeAttribute=someValue.

[Protocol Method] Delete given labels to a given entity identified by its type and unique attribute.

If labels is null/empty, no labels will be removed.

If any labels in labels set are non-existing labels, they will be ignored, only existing labels will be removed. In addition to the typeName path parameter, attribute key-value pair(s) can be provided in the following format: attr:<attrName>=<attrValue>. NOTE: The attrName and attrValue should be unique across entities, eg. qualifiedName. The REST request would look something like this: DELETE /v2/entity/uniqueAttribute/type/aType?attr:aTypeAttribute=someValue.

• This protocol method allows explicit creation of the request and processing of the response for advanced scenarios.
• Please try the simpler RemoveLabelsByUniqueAttributeAsync(String, IEnumerable<String>, String, CancellationToken) convenience overload with strongly typed models first.

Set labels to a given entity.

[Protocol Method] Set labels to a given entity.

• This protocol method allows explicit creation of the request and processing of the response for advanced scenarios.
• Please try the simpler SetLabels(String, IEnumerable<String>, CancellationToken) convenience overload with strongly typed models first.

Set labels to a given entity.

[Protocol Method] Set labels to a given entity.

• This protocol method allows explicit creation of the request and processing of the response for advanced scenarios.
• Please try the simpler SetLabelsAsync(String, IEnumerable<String>, CancellationToken) convenience overload with strongly typed models first.

Set labels to a given entity identified by its type and unique attributes.

If labels is null/empty, existing labels will all be removed.

In addition to the typeName path parameter, attribute key-value pair(s) can be provided in the following format: attr:<attrName>=<attrValue>.

NOTE: The attrName and attrValue should be unique across entities, eg. qualifiedName.

The REST request would look something like this: POST /v2/entity/uniqueAttribute/type/aType?attr:aTypeAttribute=someValue.

[Protocol Method] Set labels to a given entity identified by its type and unique attributes.

If labels is null/empty, existing labels will all be removed.

In addition to the typeName path parameter, attribute key-value pair(s) can be provided in the following format: attr:<attrName>=<attrValue>.

NOTE: The attrName and attrValue should be unique across entities, eg. qualifiedName.

The REST request would look something like this: POST /v2/entity/uniqueAttribute/type/aType?attr:aTypeAttribute=someValue.

• This protocol method allows explicit creation of the request and processing of the response for advanced scenarios.
• Please try the simpler SetLabelsByUniqueAttribute(String, IEnumerable<String>, String, CancellationToken) convenience overload with strongly typed models first.

Set labels to a given entity identified by its type and unique attributes.

If labels is null/empty, existing labels will all be removed.

In addition to the typeName path parameter, attribute key-value pair(s) can be provided in the following format: attr:<attrName>=<attrValue>.

NOTE: The attrName and attrValue should be unique across entities, eg. qualifiedName.

The REST request would look something like this: POST /v2/entity/uniqueAttribute/type/aType?attr:aTypeAttribute=someValue.

[Protocol Method] Set labels to a given entity identified by its type and unique attributes.

If labels is null/empty, existing labels will all be removed.

In addition to the typeName path parameter, attribute key-value pair(s) can be provided in the following format: attr:<attrName>=<attrValue>.

NOTE: The attrName and attrValue should be unique across entities, eg. qualifiedName.

The REST request would look something like this: POST /v2/entity/uniqueAttribute/type/aType?attr:aTypeAttribute=someValue.

• This protocol method allows explicit creation of the request and processing of the response for advanced scenarios.
• Please try the simpler SetLabelsByUniqueAttributeAsync(String, IEnumerable<String>, String, CancellationToken) convenience overload with strongly typed models first.

Update entity partially - create or update entity attribute identified by its GUID. Supports only primitive attribute type and entity references. It does not support updating complex types like arrays, and maps. Null updates are not possible.

[Protocol Method] Update entity partially - create or update entity attribute identified by its GUID. Supports only primitive attribute type and entity references. It does not support updating complex types like arrays, and maps. Null updates are not possible.

• This protocol method allows explicit creation of the request and processing of the response for advanced scenarios.
• Please try the simpler UpdateAttributeById(String, String, BinaryData, CancellationToken) convenience overload with strongly typed models first.

Update entity partially - create or update entity attribute identified by its GUID. Supports only primitive attribute type and entity references. It does not support updating complex types like arrays, and maps. Null updates are not possible.

[Protocol Method] Update entity partially - create or update entity attribute identified by its GUID. Supports only primitive attribute type and entity references. It does not support updating complex types like arrays, and maps. Null updates are not possible.

• This protocol method allows explicit creation of the request and processing of the response for advanced scenarios.
• Please try the simpler UpdateAttributeByIdAsync(String, String, BinaryData, CancellationToken) convenience overload with strongly typed models first.

Update entity partially - Allow a subset of attributes to be updated on an entity which is identified by its type and unique attribute eg: Referenceable.qualifiedName. Null updates are not possible.

In addition to the typeName path parameter, attribute key-value pair(s) can be provided in the following format:

attr:<attrName>=<attrValue>. NOTE: The attrName and attrValue should be unique across entities, eg. qualifiedName.

The REST request would look something like this: PUT /v2/entity/uniqueAttribute/type/aType?attr:aTypeAttribute=someValue.

[Protocol Method] Update entity partially - Allow a subset of attributes to be updated on an entity which is identified by its type and unique attribute eg: Referenceable.qualifiedName. Null updates are not possible.

In addition to the typeName path parameter, attribute key-value pair(s) can be provided in the following format:

attr:<attrName>=<attrValue>. NOTE: The attrName and attrValue should be unique across entities, eg. qualifiedName.

The REST request would look something like this: PUT /v2/entity/uniqueAttribute/type/aType?attr:aTypeAttribute=someValue.

• This protocol method allows explicit creation of the request and processing of the response for advanced scenarios.
• Please try the simpler UpdateByUniqueAttribute(String, AtlasEntityWithExtInfo, String, CancellationToken) convenience overload with strongly typed models first.

Update entity partially - Allow a subset of attributes to be updated on an entity which is identified by its type and unique attribute eg: Referenceable.qualifiedName. Null updates are not possible.

In addition to the typeName path parameter, attribute key-value pair(s) can be provided in the following format:

attr:<attrName>=<attrValue>. NOTE: The attrName and attrValue should be unique across entities, eg. qualifiedName.

The REST request would look something like this: PUT /v2/entity/uniqueAttribute/type/aType?attr:aTypeAttribute=someValue.

[Protocol Method] Update entity partially - Allow a subset of attributes to be updated on an entity which is identified by its type and unique attribute eg: Referenceable.qualifiedName. Null updates are not possible.

In addition to the typeName path parameter, attribute key-value pair(s) can be provided in the following format:

attr:<attrName>=<attrValue>. NOTE: The attrName and attrValue should be unique across entities, eg. qualifiedName.

The REST request would look something like this: PUT /v2/entity/uniqueAttribute/type/aType?attr:aTypeAttribute=someValue.

• This protocol method allows explicit creation of the request and processing of the response for advanced scenarios.
• Please try the simpler UpdateByUniqueAttributeAsync(String, AtlasEntityWithExtInfo, String, CancellationToken) convenience overload with strongly typed models first.

Update classifications to an existing entity represented by a guid.

[Protocol Method] Update classifications to an existing entity represented by a guid.

• This protocol method allows explicit creation of the request and processing of the response for advanced scenarios.
• Please try the simpler UpdateClassifications(String, IEnumerable<AtlasClassification>, CancellationToken) convenience overload with strongly typed models first.

Update classifications to an existing entity represented by a guid.

[Protocol Method] Update classifications to an existing entity represented by a guid.

• This protocol method allows explicit creation of the request and processing of the response for advanced scenarios.
• Please try the simpler UpdateClassificationsAsync(String, IEnumerable<AtlasClassification>, CancellationToken) convenience overload with strongly typed models first.

Update classification on an entity identified by its type and unique attributes.

[Protocol Method] Update classification on an entity identified by its type and unique attributes.

• This protocol method allows explicit creation of the request and processing of the response for advanced scenarios.
• Please try the simpler UpdateClassificationsUniqueByAttribute(String, IEnumerable<AtlasClassification>, String, CancellationToken) convenience overload with strongly typed models first.

Update classification on an entity identified by its type and unique attributes.

[Protocol Method] Update classification on an entity identified by its type and unique attributes.

• This protocol method allows explicit creation of the request and processing of the response for advanced scenarios.
• Please try the simpler UpdateClassificationsUniqueByAttributeAsync(String, IEnumerable<AtlasClassification>, String, CancellationToken) convenience overload with strongly typed models first.