Persistence path settings determine where execution results are stored, including:
- Good records
- Bad/failed records
- Drift profiles
- Anomaly metrics
- Aggregated output JSON
These paths map directly to S3, GCS, or ADLS locations configured for your tenant.
Endpoints
Get Persistence Path for an Asset
GET /catalog-server/api/rules/persistence/:assetIdUpdate Persistence Path
PUT /catalog-server/api/rules/persistence/:assetIdPath Parameters
| Name | Type | Required | Description |
|---|---|---|---|
assetId | string | Yes | Asset ID whose persistence configuration you want to manage. |
Sample Request (GET)
curl -X GET "https://{{HOST}}/catalog-server/api/rules/persistence/1202692" \ -H "accessKey: {{ACCESS_KEY}}" \ -H "secretKey: {{SECRET_KEY}}"Sample Request (Update)
curl -X PUT "https://{{HOST}}/catalog-server/api/rules/persistence/1202692" \ -H "Content-Type: application/json" \ -d '{"goodPath": "s3://mybucket/good/", "badPath": "s3://mybucket/bad/"}'Was this page helpful?