-
Notifications
You must be signed in to change notification settings - Fork 3.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[0.9.4.1] Drop Measurement for 1 DB drops all measurements of same name #4303
Comments
Actually the measurement
I guess it might be a sync or display issue in the CLI. |
@simcap, thank you for pointing this out. That is definitely unexpected behavior. Interestingly, I'm able to repro the first part with version 0.9.4.1:
but I can't seem to repro the second part:
|
This is bad. If a measurement name is shard across two databases, drop them from 1 drops them from the other. |
Thanks for the report @simcap -- we definitely need to fix this ASAP. |
The bz1, and presumably b1, engines suffer from this. However the tsm1 engine does not! |
This may actually be fixed by moving to the tsm1 engine when it is released. |
@rkuchan The second part I added (see my second comment) was to say that when I logged out of the shell and logged back in the measurement came back (so the drop only wipe one db as expected). So I was thinking more of a display sync issue in the shell. But as @otoolep points out some engines seems to suffer from this issue. Anyway thanks for the promptness, and before doing a lot of work let's ensure it is not just a shell issue. |
Any updates on this? |
@markusr fix coming soon |
fix #4303: don't drop from multiple databases
Hi,
I have a measurement called
p2p
in my dbviewers
. It happens that I also have atestviewers
db with also a measurementp2p
.I wanted to clean my
testviewers
db and drop thep2p
measurement. I did the following steps:So it is empty. The issue is that it also cleaned the db
viewers
!! Beforehand this dbviewers
had a lot of data:Now it is empty:
Is there a
from
clause where we should specify the db from which to drop the measurement. Or it is that it just wipe a measurement across all dbs?The text was updated successfully, but these errors were encountered: