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

Auto USE keyspace in session once Pillar is initialized #16

Open
fkoehler opened this issue Jul 14, 2014 · 0 comments
Open

Auto USE keyspace in session once Pillar is initialized #16

fkoehler opened this issue Jul 14, 2014 · 0 comments

Comments

@fkoehler
Copy link
Contributor

With 2.0.0 I run into the issue that when creating a new keyspace with Pillar.initilaize I get an
[error] An error occurred while performing task: com.datastax.driver.core.exceptions.InvalidQueryException: no keyspace has been specified com.datastax.driver.core.exceptions.InvalidQueryException: no keyspace has been specified
when running the real migrations. One solution is to execute
session.execute("USE $keyspace")
AFTER Pillar.initialize run but before Pillar.migrate

I think Pillar should do this automatically, meaning in Pillar.migrate it should "USE $keyspace"

fkoehler added a commit to fkoehler/sbt-pillar-plugin that referenced this issue Jul 14, 2014
- Upgrade to pillar 2.0.0
- Added cassandra.replicationFactor config option to allow configuring different replication factors than 3. This is used in testing if one runs against a single node.
- Added the Tasks and Config entries to the Test and Default configuration so one can provide different config for testing and "normale" usage
- Auto "USE keyspace" after Pillar.initialize to select the proper keyspace. Could be fixed with comeara/pillar#16
- Version bump to 1.0.0 as it is used in production now
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

No branches or pull requests

1 participant