You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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"
The text was updated successfully, but these errors were encountered:
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
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"
The text was updated successfully, but these errors were encountered: