How It Works

This page describes how Corvus processes delete-by-query requests for entities and temporal entities.

Entity Purge (/ngsi-ld/v1/entities)

Corvus forwards your query to the broker’s GET /ngsi-ld/v1/entities, paginates through all results, deduplicates IDs, and sends a single batch delete to POST /ngsi-ld/v1/entityOperations/delete.

You pass query parameters as you would for a normal entity query (for example, type, idPattern, q, geometry). Corvus handles pagination internally; you do not need to manage limit or offset.

Temporal Entity Purge (/ngsi-ld/v1/temporal/entities)

Corvus supports two purge strategies for temporal entities:

  • Simple queries (whole-entity filters): Deletes entire temporal entities via DELETE /ngsi-ld/v1/temporal/entities/{id}

  • Complex queries (attribute or temporal filters): Fetches full temporal representations, extracts instance IDs, and deletes each instance via DELETE /ngsi-ld/v1/temporal/entities/{id}/attrs/{attr}/{instanceId}

In both cases, Corvus paginates through results and performs deletes concurrently with configurable parallelism and retries.