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

Quotation marks (and likely other special characters) in bucket name is accepted on bucket creation but queries fail for all data #19179

Closed
ghost opened this issue Aug 3, 2020 · 1 comment · Fixed by #19222

Comments

@ghost
Copy link

ghost commented Aug 3, 2020

List the minimal actions needed to reproduce the behavior.

  1. Create a bucket called ["Foobar" 2020-08-03 12:07:40.409 uuid-of-an-experiment] with quotation marks without [ and], with a couple of tags
  2. Go to influxdb data explorer UI and try to load the tag list
  3. Notice "Failed to load tag keys" in UI and in browser HTTP debugger Network request: 400 - error @1:yy-1:xx: undefined identifier Foobar

Expected behavior:
Invalid bucket name shouldn't even be accepted if the queries cannot work for it. Sanitize the bucketname requested or fail the request immediately, with a descriptive error message like "Invalid character " detected".

Alternatively, support special characters like questions marks in the queries being performed by the explorer so that the identifier attempted is "Foobar" not Foobar.

Actual behavior:
Bucket is created, but querying tags and showing data fails. In UI it looks like a problem with the tags or data, but in reality the problem is the bucket name.

Environment info:

influxdb running as a linux container

Image: quay.io/influxdb/influxdb:2.0.0-beta
Image ID: c25b1da9b9cc (I believe this is beta 15?)

@russorat
Copy link
Contributor

russorat commented Aug 3, 2020

@Mierpo thanks for the issue. We will take a look.

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

Successfully merging a pull request may close this issue.

2 participants