When a delete is detected on either the Source or the Destination, Delete Policy determines how DataHub will behave.
Ignore items deleted from both source and destination
Ignore Both: When a delete is detected on either the Source or the Destination, the application will ignore and take no action. This is the system default option.
Extended Description: Ignore Both is the system default for Delete Policy. Based on your transfer type selected, you can expected the following behavior for Delete Policy Ignore Both:
Synchronize - When a delete is detected on either the source or the destination, the application will ignore and take no action.
Copy - Delete Policy Ignore Both is not applicable. With transfer type Copy, the application will always use the Ignore Source Delete Policy, so Delete Policy Ignore Both would not be applicable
Migrate - Delete Policy Ignore Both is not applicable. With transfer type Migrate, the application does not run change/delete detection on subsequent job runs, Delete Policy Ignore Both would not be applicable.
Publish - Delete Policy Ignore Both is not applicable. Based on the definition of transfer type Publish, it must make deletes on the Destination to ensure it matches the Source, so Delete Policy Ignore Both would not be applicable.
Move - Delete Policy Ignore Both is not applicable. Based on the definition of transfer type Move, it must evaluate the Source, transfer all content to the destination, then delete everything from the Source, so Delete Policy Ignore Both would not be applicable.
Copy Folder Structure - Delete Policy Ignore Both is not applicable. With transfer type Copy Folder Structure, the application does not run change/delete detection on subsequent job runs, Delete Policy Ignore Both would not be applicable.
Ignore items deleted from source
Ignore Source: When a delete is detected on the Source, the application will ignore and take no action. If a delete is detected on the Destination, the delete will propagate.
Extended Description: Based on your transfer type selected, you can expected the following behavior for Delete Policy Ignore Source:
Synchronize - When a delete is detected on the source, the application will ignore and take no action. If a delete is detected on the destination, the delete will still occur.
Copy - When a delete is detected on the source, the application will ignore and take no action. If a delete is detected on the destination, the delete will still occur.
Migrate - Delete Policy Ignore Source is not applicable. With transfer type Migrate, the application does not run change/delete detection on subsequent job runs, Delete Policy Ignore Source would not be applicable.
Publish - Delete Policy Ignore Source is not applicable. Based on the definition of transfer type Publish, it must make deletes on the Destination to ensure it matches the Source, so Delete Policy Ignore Source would not be applicable.
Move - Delete Policy Ignore Source is not applicable. Based on the definition of transfer type Move, it must evaluate the Source, transfer all content to the destination, then delete everything from the Source, so Delete Policy Ignore Source would not be applicable.
Copy Folder Structure - Delete Policy Ignore Source is not applicable. With transfer type Copy Folder Structure, the application does not run change/delete detection on subsequent job runs, Delete Policy Ignore Source would not be applicable.
Ignore items deleted from destination
Ignore Destination: When a delete is detected on the Destination, the application will ignore and take no action. If a delete is detected on the Source, the delete will propagate.
Extended Description: Based on your transfer type selected, you can expected the following behavior for Delete Policy Ignore Destination:
Synchronize - When a delete is detected on the Destination, the application will ignore and take no action. If a delete is detected on the Source, the delete will still occur.
Copy - Delete Policy Ignore Destination is not applicable. With transfer type Copy, the application will always use the Ignore Source Delete Policy, so Delete Policy Ignore Destination would not be applicable.
Migrate - Delete Policy Ignore Destination is not applicable. With transfer type Migrate, the application does not run change/delete detection on subsequent job runs, Delete Policy Ignore Destination would not be applicable.
Publish - Delete Policy Ignore Destination is not applicable. Based on the definition of transfer type Publish, it must make deletes on the Destination to ensure it matches the Source, so Delete Policy Ignore Destination would not be applicable.
Move - Delete Policy Ignore Destination is not applicable. Based on the definition of transfer type Move, it must evaluate the Source, transfer all content to the destination, then delete everything from the Source, so Delete Policy Ignore Destination would not be applicable.
Copy Folder Structure - Delete Policy Ignore Destination is not applicable. With transfer type Copy Folder Structure, the application does not run change/delete detection on subsequent job runs, Delete Policy Ignore Destination would not be applicable.
Mirror the deletion when items are deleted from source
Mirror: When a delete is detected on either the Source or the Destination, the application will take action and delete the file on the opposing side. This option will never ignore delete events.
Extended Description: Based on your transfer type selected, you can expected the following behavior for Delete Policy Mirror:
Synchronize - When a delete is detected on either the Source or the Destination, the application will take action and delete the file on the opposing side. This option will never ignore delete events.
Copy - When a delete is detected on the Source, the application will take action and delete the file on the Destination on subsequent job runs. This option will never ignore delete events.
Migrate - Delete Policy Mirror is not applicable. With transfer type Migrate, the application does not run change/delete detection on subsequent job runs, Delete Policy Mirror would not be applicable.
Publish - Delete Policy Mirror is not applicable. Based on the definition of transfer type Publish, it must make deletes on the Destination to ensure it matches the Source, so Delete Policy Mirror would not be applicable.
Move - Delete Policy Mirror is not applicable. Based on the definition of transfer type Move, it must evaluate the Source, transfer all content to the Destination, then delete everything from the Source, so Delete Policy Mirror would not be applicable.
Copy Folder Structure - Delete Policy Mirror is not applicable. With transfer type Copy Folder Structure, the application does not run change/delete detection on subsequent job runs, Delete Policy Mirror would not be applicable.
Related:
Example JSON
Configuration options include:
- ignore_both (default)
- ignore_source
- ignore_destination
- mirror
POST {{url}}v1/jobs
|
|