DROP ALL TABLES ends with error when telemetry is enabled
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 17.3k
- Forks
- 1.6k
- Avg merge
- 5d 10h
- Merged PRs (30d)
- 28
Description
Describe the bug
When telemetry is enabled (which is the default) issuing:
DROP ALL TABLES;
ends with failed to drop tables ['telemetry': [-1] could not lock 'telemetry' [reason='telemetry']] error.
Command should skip telemetry table instead.
To reproduce
No response
Expected Behavior
No response
Environment
- **QuestDB version**:7.3.6-SNAPSHOT
- **OS**:
- **Browser**:
Additional context
No response
Contributor guide
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
Start by reproducing DROP ALL TABLES; with telemetry enabled on QuestDB 7.3.6-SNAPSHOT, then trace the command's handling of the telemetry table. Done means the command succeeds while skipping telemetry instead of reporting a lock error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, sql
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100