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

Permit usage of "_" character in keyspace name #6755

Closed
Smita8081 opened this issue Sep 21, 2020 · 5 comments
Closed

Permit usage of "_" character in keyspace name #6755

Smita8081 opened this issue Sep 21, 2020 · 5 comments
Labels
Component: Cluster management Type: Enhancement Logical improvement (somewhere between a bug and feature)

Comments

@Smita8081
Copy link

Smita8081 commented Sep 21, 2020

Hi, I have been struggling to create keyspace having _ in its name, for instance nova_api. Seems like there is restriction in using _ character.

Feature Description

Permit usage of '_' character in keyspace name.

Use Case(s)

Since my database name have _ in its name and that Vitess keyspace doesn't allow to create keyspace name with _ in it. So i had to do a lot many changes in the application to direct the request from earlier mentioned database name(nova_api) to now (novaapi). This is something I really want to avoid so as to make the integration of Vitess cluster with application more effortless.

@harshit-gangal harshit-gangal added the Type: Enhancement Logical improvement (somewhere between a bug and feature) label Sep 21, 2020
@deepthi
Copy link
Member

deepthi commented Oct 2, 2020

Vitess itself allows _ in keyspace names. It seems like you are using the operator?

@Smita8081
Copy link
Author

yes I am using operator.

@deepthi
Copy link
Member

deepthi commented Oct 5, 2020

Can you create an issue here instead?
https://github.com/planetscale/vitess-operator/issues

@maZahaca
Copy link

I've just created one in vitess-operator: planetscale/vitess-operator#164

@aquarapid
Copy link
Contributor

This is supported now; planetscale/vitess-operator#164 closed; closing this issue as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Component: Cluster management Type: Enhancement Logical improvement (somewhere between a bug and feature)
Projects
None yet
Development

No branches or pull requests

6 participants