Avoid calling CREATE KEYSPACE|TABLE IF NOT EXISTS …
unnecessarily
#655
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This also is a fix for AstraDB, which throws an exception if you try to
CREATE KEYSPACE IF NOT EXISTS …
This PR looks like more change than it really is.
It is actually only two lines, the body of both the
ensureKeyspaceExists()
andensureTableExists(..)
methods are wrapped in anif
statement.spring-ai/vector-stores/spring-ai-cassandra/src/main/java/org/springframework/ai/vectorstore/CassandraVectorStoreConfig.java
Line 471 in c07663a
spring-ai/vector-stores/spring-ai-cassandra/src/main/java/org/springframework/ai/vectorstore/CassandraVectorStoreConfig.java
Line 568 in c07663a