influxdata / influxdata/docs-v2

Versioning data vs deleting data: best practices, patterns, and examples

Open
#4,819 1 comment 0 reactions 0 assignees View on GitHub
InfluxDB v3
Dominant language
JavaScript
Stars
82
Forks
326
Avg merge
1d 1h
Merged PRs (30d)
82

Description

Deleting data in Cloud IOx

- Best practice for time series data is to add version tags or other tags to points as you write them. Then, instead of deleting (invalid?) data points, use tag filters in your queries to retrieve the versioned data you want.
- Deleting data is not currently supported.
- Deleting data may be necessary if you need to:
- Decommission (expired?) data.
- Remove data for policy reasons.

##### Relevant URLs
- _Provide relevant URLs_

Contributor guide

No contributing guide indexed for this repository

Research direction

The issue names no files, tests, or concrete entry points, and its relevant-URL section is still a placeholder. First clarify the supported deletion behavior and the intended versioning guidance for Cloud IOx. Done should include agreed best practices, deletion considerations, and concrete patterns or examples in the documentation.

Written by the indexing model from the issue text.

Assessment

Domain
databases, documentation
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.