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

API returns inconsistent results for drop requests on non-existent databases #8794

Closed
smolse opened this issue Sep 6, 2017 · 1 comment
Closed

Comments

@smolse
Copy link

smolse commented Sep 6, 2017

InfluxDB version: 1.3.1

When running drop continuous query request on non-existent database:

$ curl localhost:8086/query --data-urlencode 'q=drop continuous query "whatever" on "non_existent_db"'
{"results":[{"statement_id":0,"error":"database not found: non_existent_db"}]}

When running drop retention policy request on non-existent database:

$ curl localhost:8086/query --data-urlencode 'q=drop retention policy "whatever" on "non_existent_db"'
{"results":[{"statement_id":0}]}

Expected result would be to get error also for drop retention policy request.

@smolse smolse changed the title API returns inconsistent results for drop requests on non-existing databases API returns inconsistent results for drop requests on non-existent databases Sep 6, 2017
@andrewhare andrewhare self-assigned this Sep 20, 2017
@smolse
Copy link
Author

smolse commented Jul 20, 2018

I believe this was fixed in #8878.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants