You must provide a human-readable name for your data domain.
You can chain onto the creator any other enrichment, for example choosing a different icon or color to represent the domain.
You then need to build the object.
You can then save() the object you've built to create the new data domain in Atlan. Because this operation will persist the asset in Atlan, you must provide it an AtlanClient through which to connect to the tenant.
You must provide a human-readable name for your data domain.
You can chain onto the creator any other enrichment, for example choosing a different icon or color to represent the domain.
You then need to build the object.
You can then save() the object you've built to create the new data domain in Atlan. Because this operation will persist the asset in Atlan, you must provide it an AtlanClient through which to connect to the tenant.
You must provide a human-readable name for your data domain.
To create subdomain, you must provide the parent domain with at least its qualifiedName.
You can chain on other enrichment, like above, but ultimately then need to build the object.
You can then save() the object you've built to create the new data subdomain in Atlan. Because this operation will persist the asset in Atlan, you must provide it an AtlanClient through which to connect to the tenant.
You must provide a human-readable name for your data domain.
To create subdomain, you must provide the parent domain with at least its qualifiedName.
You can chain on other enrichment, like above, but ultimately then need to build the object.
You can then save() the object you've built to create the new data subdomain in Atlan. Because this operation will persist the asset in Atlan, you must provide it an AtlanClient through which to connect to the tenant.
The qualifiedName should follow the pattern: <parentQualifiedName>/domain/<lowerCamelCaseName>.
You must provide the qualifiedName of the parent domain.
Provide a superDomainQualifiedName for the data domain under which you want to create this sub-domain.
If creating a sub-domain under another sub-domains (ie. nested sub-domains), this should be the qualified name of the root-level domain.
You must also specify a relationship to the parent domain, in this example through its qualifiedName.
DataDomaindomain=DataDomain.updater("default/domain/marketing",// (1)"Marketing").userDescription("Now with a description!")// (2).build();// (3)AssetMutationResponseresponse=domain.save(client);// (4)
Use the updater() method to update a data domain, providing the qualifiedName and name of the data domain.
You can chain onto the updater any other enrichment, for example changing the domain's description.
You then need to build the object.
You can then save() the object you've built to update the data domain in Atlan. Because this operation will persist the asset in Atlan, you must provide it an AtlanClient through which to connect to the tenant.
Update a data domain
1 2 3 4 5 6 7 8 9101112
frompyatlan.client.atlanimportAtlanClientfrompyatlan.model.assetsimportDataDomainclient=AtlanClient()data_domain=DataDomain.updater(# (1)qualified_name="default/domain/marketing",# (2)name="Marketing",# (3))data_domain.user_description="Now with a description!"# (4)response=client.asset.save(data_domain)# (5)
Use the updater() method to update a data domain.
You must provide the qualifiedName of the data domain.
You must provide the name of the data domain.
You can then add on any other updates, such as changing the user description of the data domain.
To update the data domain in Atlan, call the save() method with the object you've built.
Update a data domain
12345
valdomain=DataDomain.updater("default/domain/marketing",// (1)"Marketing").userDescription("Now with a description!")// (2).build()// (3)valresponse=domain.save(client)// (4)
Use the updater() method to update a data domain, providing the qualifiedName and name of the data domain.
You can chain onto the updater any other enrichment, for example changing the domain's description.
You then need to build the object.
You can then save() the object you've built to update the data domain in Atlan. Because this operation will persist the asset in Atlan, you must provide it an AtlanClient through which to connect to the tenant.
POST /api/meta/entity/bulk
1 2 3 4 5 6 7 8 9101112
{"entities":[{"typeName":"DataDomain",// (1)"attributes":{"name":"Marketing",// (2)"qualifiedName":"default/domain/marketing",// (3)"userDescription":"Now with a description!"// (4)},}]}
The typeName must be exactly DataDomain.
Human-readable name for your data domain.
You must provide the the qualifiedName of the domain to update.
You can add on any other updates, such as changing the user description of the data domain.
To archive a data domain in Atlan, call the DataDomain.delete() method with the GUID of the data domain. Because this operation will archive the asset in Atlan, you must provide it an AtlanClient through which to connect to the tenant.
To archive a data domain in Atlan, call the DataDomain.delete() method with the GUID of the data domain. Because this operation will archive the asset in Atlan, you must provide it an AtlanClient through which to connect to the tenant.
To permanently delete a data domain in Atlan, call the DataDomain.purge() method with the GUID of the data domain. Because this operation will remove the asset from Atlan, you must provide it an AtlanClient through which to connect to the tenant.
To permanently delete a data domain in Atlan, call the DataDomain.purge() method with the GUID of the data domain. Because this operation will remove the asset from Atlan, you must provide it an AtlanClient through which to connect to the tenant.