Fix panic during wildcard expansion if no database specified #2994
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
It is not used by the code -- the database on the measurement object that determines the target database.
otoolep
force-pushed
the
panic_no_db_in_url
branch
from
1731897 to
461cccc
Compare
otoolep
changed the title
otoolep
changed the title
Statements were only being normalized if a default database was included in the query (usually via the query param 'db'). However if no default database was included, and none was an explicit part of the measurement name, no database-existence check was run. This result in a later panic with wildcard expansion.
otoolep
force-pushed
the
panic_no_db_in_url
branch
from
461cccc to
b758a23
Compare
|
+1 |
otoolep
added a commit
that referenced
this pull request
Jun 15, 2015
Fix panic during wildcard expansion if no database specified
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Statements were only being normalized if a default database was included
in the query (usually via the query param 'db'). However if no default
database was included, and none was an explicit part of the measurement
name, no database-existence check was run. This results in a later panic
with wildcard expansion.
Fixes #2932