Documentation

Delete predicate syntax

This page documents an earlier version of InfluxDB. InfluxDB v2.6 is the latest stable version. View this page in the v2.6 documentation.

InfluxDB uses an InfluxQL-like predicate syntax to determine what data points to delete. InfluxDB uses the delete predicate to evaluate the series keys of points in the time range specified in the delete request. Points with series keys that evaluate to true for the given predicate are deleted. Points with series keys that evaluate to false are preserved.

A delete predicate is comprised of one or more predicate expressions. The left operand of the predicate expression is the column name. The right operand is the column value. Operands are compared using comparison operators. Use logical operators to combine two or more predicate expressions.

Example delete predicate
key1="value1" AND key2="value"

With InfluxDB 2.3, delete predicates can use any column or tag except _time, _field,or _value.

Logical operators

Logical operators join two or more predicate expressions.

OperatorDescription
ANDBoth left and right operands must be true for the expression to be true.

Comparison operators

Comparison operators compare left and right operands and return true or false.

OperatorDescriptionExampleResult
=Equal to"abc"="abc"true

Delete predicate examples

Delete points by measurement

The following will delete points in the sensorData measurement:

_measurement="sensorData"

Delete points by tag set

The following will delete points from the prod-1.4 host in the us-west region:

host="prod-1.4" AND region="us-west"

Limitations

The delete predicate syntax has the following limitations.

  • Delete predicates do not support regular expressions.
  • Delete predicates do not support the OR logical operator.
  • Delete predicates only support equality (=), not inequality (!=).
  • Delete predicates can use any column or tag except _time , _field, or _value.

Was this page helpful?

Thank you for your feedback!


Set your InfluxDB URL

Linux Package Signing Key Rotation

All signed InfluxData Linux packages have been resigned with an updated key. If using Linux, you may need to update your package configuration to continue to download and verify InfluxData software packages.

For more information, see the Linux Package Signing Key Rotation blog post.

InfluxDB Cloud backed by InfluxDB IOx

All InfluxDB Cloud organizations created on or after January 31, 2023 are backed by the new InfluxDB IOx storage engine. Check the right column of your InfluxDB Cloud organization homepage to see which InfluxDB storage engine you’re using.

If powered by IOx, this is the correct documentation.

If powered by TSM, see the TSM-based InfluxDB Cloud documentation.

InfluxDB Cloud backed by InfluxDB TSM

All InfluxDB Cloud organizations created on or after January 31, 2023 are backed by the new InfluxDB IOx storage engine which enables nearly unlimited series cardinality and SQL query support. Check the right column of your InfluxDB Cloud organization homepage to see which InfluxDB storage engine you’re using.

If powered by TSM, this is the correct documentation.

If powered by IOx, see the IOx-based InfluxDB Cloud documentation.

State of the InfluxDB Cloud (IOx) documentation

The new documentation for InfluxDB Cloud backed by InfluxDB IOx is a work in progress. We are adding new information and content almost daily. Thank you for your patience!

If there is specific information you’re looking for, please submit a documentation issue.