questdb / questdb/documentation
InfluxDB migration improvement
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13
- Forks
- 44
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 26
Description
The influxdb migration page does not explain buckets vs buckets, tags vs symbols and so on. We should make something similar to what influx3 has to explain migrating from influx2.
Also, when we do this, we can change the current sparse table example to do it using a matview and using TTL on the original table, which probably makes sense.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Locate the InfluxDB migration page and compare its guidance with the referenced influx3 migration material. Clarify buckets versus tables, tags versus symbols, and related concepts; then revise the sparse table example to use a materialized view and TTL on the original table, with the page content serving as the completion check.
Written by the indexing model from the issue text.
Assessment
- Domain
- databases, documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100