influxdata / influxdata/influxdb
BUG Old tags show up after dropping measurement
- Dominant language
- Rust
- Stars
- 31.7k
- Forks
- 3.7k
- Avg merge
- 13h 37m
- Merged PRs (30d)
- 8
Description
__Steps to reproduce:__
List the minimal actions needed to reproduce the behavior.
1. use influx_stress insert data to database test, measurement m1, write until tsi files created.
2. show tag keys from m1 result=[t1,t2,t3,t4,t5,t6]
3. drop measurement m1 return without error
4. insert m1,t1=1 f1=1
5. show tag keys from m1 result=[t1,t2,t3,t4,t5,t6]
__Expected behavior:__
step 5 show tag keys from m1 should return result=[t1], because in step 4, insert a point which only has one tag, t1
__Actual behavior:__
step 5 show tag keys from m1 return result=[t1,t2,t3,t4,t5,t6], tags in old measurement "m1" reappeared, like t2,t3,t4,t5,t6
__Environment info:__
Centos 7, influxdb 1.8.0
__Config:__
use default config, created by command "influxd config"
the BUG seems only appear when tsi file created.
I notice the issue #10052 "Old fields and tags show up after dropping measurement and rewriting", show field keys result is OK, but show tag keys seem wrong, it apparently seems a serious BUG.
Contributor guide
Research direction
Start by reproducing the sequence with influx_stress, including TSI file creation, then compare tag-key results after dropping and reinserting measurement m1. Review issue #10052 for related behavior. Done means old tags no longer reappear and the drop/reinsert sequence has regression coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100