-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Uppercase keyspace causes Kong migrations to fail #249
Labels
Comments
Actually migrations are successful but a keyspace will always be lower case, so a fix would be to force it to be lower case in the configuration loading I guess |
Sorry, I meant the keyspace creation is successful* |
@thibaultcha is this closed? |
No |
thibaultcha
added a commit
that referenced
this issue
May 28, 2015
Ok fixed by #271! |
ctranxuan
pushed a commit
to streamdataio/kong
that referenced
this issue
Aug 25, 2015
Fix Kong#249 Former-commit-id: 1a908b7a82b559a1da1352473293cd64cd11d4e4
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
$ kong start [INFO] Using configuration: /etc/kong/kong.yml [INFO] Proxy port.........8000 Admin API port.....8001 Database...........cassandra keepalive=60000 port=9042 timeout=1000 hosts=kongdb.org keyspace=Yoda [INFO] Database not initialized. Running migrations... [ERR] Cassandra error: Cassandra returned error (Invalid): "Keyspace 'yoda' does not exist"
The keyspace is lowercase in the error so I changed it to lowercase in
kong.yml
and it then worked.The text was updated successfully, but these errors were encountered: