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

Fix typos #9708

Merged
merged 2 commits into from
May 2, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -12,5 +12,5 @@ Changelog scripts MUST tell explicitly which keyspace is used:
- by using `USE myKeyspace;` directive at the beginning of a script
- or by prepending each table with the keyspace it belongs to: `CREATE TABLE IF NOT EXISTS myKeyspace.myTable`

Second approach is recommended: it allows to not switch keyspace at runtime if there's many of them.
Second approach is recommended: it allows to not switch keyspace at runtime if there are many of them.
See [warn-if-set-keyspace section](https://docs.datastax.com/en/developer/java-driver/latest/manual/core/configuration/reference/) for more info.
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ Similar to Liquibase, JHipster Lite provides a tool to apply your CQL migration
- The tool is not run by the application itself when it is started but inside a Docker container or manually
- All CQL scripts must follow the pattern `{timestamp}_{description}.cql` and be placed in the changelog directory: `src/main/resources/config/cql/changelog/`
- All non already applied scripts located in the changelog directory are applied in alphabetical order (ie: following the timestamp)
- Because Cassandra is not a transactional database, if an error happen before inserting the metadata in the table used by the tool there is a risk to have your CQL migration script run multiple times
- Because Cassandra is not a transactional database, if an error happens before inserting the metadata in the table used by the tool there is a risk to have your CQL migration script run multiple times

Some information on the tool:

Expand Down
Loading