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

Keyspace creation #100

Open
wind57 opened this issue Sep 21, 2021 · 1 comment
Open

Keyspace creation #100

wind57 opened this issue Sep 21, 2021 · 1 comment

Comments

@wind57
Copy link

wind57 commented Sep 21, 2021

Is there a way to create the keyspace before applying change sets? Our use case is that we have multiple envs, with a lot of keyspaces, that all have different names. Ideally, creating the keyspace should be tracked by liquibase too, not as a separate activity outside liquibase lifecycle.

Am I correct that this is not possible and it is assumed that keyspace must exist? This would be a pity, since it would basically mean it is a useless tool for us :( I hope I am missing something.

Thank you

┆Issue is synchronized with this Jira Bug by Unito

@wind57
Copy link
Author

wind57 commented Sep 21, 2021

I hoped something like this would work

"preConditions": [
        {
          "dbmsType": "cassandra",
          "onFail": "HALT",
          "sqlCheck": {
            "sql": "CREATE KEYSPACE IF NOT EXISTS Killer_Video WITH replication = {'class':'SimpleStrategy', 'replication_factor':1};",
            "expectedResult": 1
          }
        }
      ]

but this has failed no matter what I tried.


Oh I just saw that this is not related to cassandra, liquibase can't do that, in general. I guess, this means we will not be using this.

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