Skip to content
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

Info about deleted data after DELETE/DROP comand #7691

Closed
dstreppa opened this issue Dec 6, 2016 · 4 comments
Closed

Info about deleted data after DELETE/DROP comand #7691

dstreppa opened this issue Dec 6, 2016 · 4 comments
Labels
1.x area/influxql Issues related to InfluxQL query language kind/feature-request wontfix

Comments

@dstreppa
Copy link

dstreppa commented Dec 6, 2016

Feature Request

Proposal: [Description of the feature]
After a DELETE/DROP comand an explanatory string shows the number of deleted data.

Current behavior: [What currently happens]

DELETE from trevano WHERE time>='2016-12-05T12:00:00Z' and time<='2016-12-06T00:00:00Z'

Desired behavior: [What you would like to happen]

DELETE from trevano WHERE time>='2016-12-05T12:00:00Z' and time<='2016-12-06T00:00:00Z'
1000 samples deleted from measurement trevano

Use case: [Why is this important (helps with prioritizing requests)]
To have a a fast idea of the deleted data. Considering the query above, if I receive as output "1000000 samples deleted from measurement trevano" instead of 1000 I can easily understand that I did an error.

@e-dard e-dard added kind/feature-request area/influxql Issues related to InfluxQL query language labels Dec 7, 2016
@e-dard
Copy link
Contributor

e-dard commented Dec 7, 2016

@dstreppa thanks for the request. Currently drops/deletes are reasonably cheap because of the data structures we use to store data in InfluxDB. We have do do some pruning and cleaning up, but we don't need to find all the relevant points/series and delete them one by one. As such it's not trivial to know how many points were dropped.

I think if we were going to add this feature we would have to query for the data internally before we did a delete/drop, so it seems like this is no different to you running the query and checking the output prior to the drop/delete command.

Maybe some other Influxers will have some input on this.

@dstreppa
Copy link
Author

dstreppa commented Dec 7, 2016

@e-dard thank you for the clear answer, I understand your point. I already do the check before and after the command to be sure.

@dgnorton dgnorton added the 1.x label Jan 7, 2019
@stale
Copy link

stale bot commented Jul 24, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix label Jul 24, 2019
@stale
Copy link

stale bot commented Jul 31, 2019

This issue has been automatically closed because it has not had recent activity. Please reopen if this issue is still important to you. Thank you for your contributions.

@stale stale bot closed this as completed Jul 31, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1.x area/influxql Issues related to InfluxQL query language kind/feature-request wontfix
Projects
None yet
Development

No branches or pull requests

3 participants