- URL:
- https://<adminRoot>/services/<serviceName>/FeatureServer/cleanupChangeTracking
- Methods:
POST
Description
Change tracking information stored in each feature service layer (enabled for Change Tracking) might grow very large. The change tracking info used by the feature service to determine the change generation number and the features that have changed for a particular generation. Clients can purge the change tracking content if the changes are already synced-up to all clients and the changes are no longer needed.
The change tracking cleaned only supported on the feature service admin API. Only the owner or the organization administrator can cleanup change tracking information.
Request Parameters
| Parameter | Details |
|---|---|
| Description: A comma separated list of the layers. Syntax: layers=[<layer1>, <layer2>] Example: layers=0,1,2 or layers=[0,1,2] |
| Description: The retention period to use when cleaning up the change tracking information. Change tracking information will be cleaned up if they are older than the retention period. Example: retentionPeriod=30 |
| Description: The units of the retention period. Syntax: "retentionPeriodUnits" : <days | seconds, minutes, hours> Example: "retentionPeriodUnits" : "days" |
| Description: In addition to the retention period, the change tracking can be cleaned by its generation numbers. Older tracking information that has older generation number than the Example: "minServerGen" : 56000000 |
| Description: The change tracking can also be cleaned by the Example: "replicaId" : "b62e9db7-507c-443d-3473-8a1f7a7e9fa" |
| Description: Support options for asynchronous processing. The default format is Value: true | false |
| Description: The response format. The default value is Value: |
Example Usage
Parameters:
"layer" : 0
"retentionPeriod" : 60
"retentionPeriodUnits" : "days"
"f" : "json"
JSON Response Example
{"success" : true}