EVICT

The EVICT operation removes one or more documents from the local Ditto store, deleting them entirely without flagging (tombstone) as deleted to remote peers:

DQL


In this syntax:

  • your_collection_name is the name of the collection from which you want to retrieve the data.
  • [condition] represents the condition or criteria that determine which documents should be evicted from the local peer.

Examples Deleting Documents

Here, documents from the cars collection that have the document ID 123 get removed from the Ditto store:

DQL


As another example, the following snippet, once executed, results in the deletion of documents with timestamps greater than a certain value:

DQL


Removing Fields from Documents

To remove a specific field from a document, use an UPDATE statement to tombstone that field. A tombstone is a flag signaling to remote peers that the DQL data type has been removed. See: UPDATE

Removing Data from Big Peer

EVICT is not currently available for the Big Peer, although it's in development. To learn more about removing data from your Big Peer instance, see Writing: HTTP (Legacy) .

Developing an Eviction Strategy

Removing data from a distributed database is a difficult problem, and memory management requires careful consideration of both subscriptions and evictions.

To learn more about our recommended strategies, see DELETE.

Updated 10 Oct 2024
Did this page help you?