DeleteFromCache
Step reads data from cache using save_key, sets the returned data for next step.
Added in version 1.0.0.
Friendly name:
Cache DeleteStep class:
base_steps_syncpack.steps.DeleteFromCache.DeleteFromCacheStep version:
1.2.1Required parameters:
save_key,lookup_type
Parameters
Name |
Type |
Required |
Default |
Description |
|---|---|---|---|---|
|
string |
yes |
– |
The key which will be deleted Example: |
|
enum |
yes |
|
How to perform the search from cache. Can either be ‘equals’, or ‘like’ |
|
boolean |
no |
|
Try to combine the results into a single list |
Every step also accepts the platform parameters common to all steps – see Platform parameters.
Dependencies
Inherits from:
DeleteFromCache->BaseStep->SerializableExternal packages:
couchbase,ipaascommon,ipaascore,isbaseutils
Note
The description shown above reads “Step reads data from cache using
save_key…”. That text is copy-pasted from ReadFromCache and is
wrong — this step deletes. Tracked as a source fix; the generated
description will correct itself once the source does.
Behaviour
Deletes matching cache documents. lookup_type selects the match:
likedelete_from_logs_bucket_startswith— prefix match, which also removes thekey::1,key::2chunks written by SaveToCache.equalsdelete_from_logs_bucket— exact key.
Both fall back to an N1QL DELETE ... WHERE META().id LIKE (INT-6201), wrapped
with @retry(CouchbaseException, tries=3).
Outputs
None. The step never calls save_data_for_next_step, so whatever the
previous step produced is what the next step sees. Do not place it mid-pipeline
expecting it to forward data.
Notes
merge_resultsis declared but unused — there is no downstream data to merge.likewith a shortsave_keydeletes by prefix and will take every key that starts with it. Scope the key carefully; there is no dry-run.Deleting a chunked entry needs
like. Withequalsyou remove the base document and orphankey::1onwards, which then look like a partial cache to ReadFromCache.