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

fix: allow .(dot) literal in table name #2483

Merged

Conversation

MichaelScofield
Copy link
Collaborator

I hereby agree to the terms of the GreptimeDB CLA

What's changed and what's your intention?

It's common for OpenTSDB metrics to use .(dot) literal in their names.

Checklist

  • I have written the necessary rustdoc comments.
  • I have added the necessary unit tests and integration tests.

Refer to a related PR or issue link (optional)

@codecov
Copy link

codecov bot commented Sep 25, 2023

Codecov Report

Merging #2483 (5da3af9) into develop (73842f1) will decrease coverage by 0.08%.
Report is 17 commits behind head on develop.
The diff coverage is 9.52%.

Additional details and impacted files
@@             Coverage Diff             @@
##           develop    #2483      +/-   ##
===========================================
- Coverage    84.97%   84.90%   -0.08%     
===========================================
  Files          725      729       +4     
  Lines       115463   115910     +447     
===========================================
+ Hits         98120    98416     +296     
- Misses       17343    17494     +151     

@evenyag
Copy link
Contributor

evenyag commented Sep 25, 2023

We should validate the table name before creating or renaming a table.

@MichaelScofield MichaelScofield added this pull request to the merge queue Sep 27, 2023
Merged via the queue into GreptimeTeam:develop with commit ccd6de8 Sep 27, 2023
@MichaelScofield MichaelScofield deleted the fix/allow-dot-tablename branch September 27, 2023 12:00
paomian pushed a commit to paomian/greptimedb that referenced this pull request Oct 19, 2023
* fix: allow `.`(dot) literal in table name

* fix: resolve PR comments
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

Successfully merging this pull request may close these issues.

3 participants