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
Bug description
With latest version of 1.0.0-M3, even when using the base package for ChromaDB and manually initialising the collections, it's trying to create a collection messing up the Buildpacks and CDS.
Environment
Spring AI version 1.0.0-M3
Spring Boot version 3.3.4
ChromaDB version 0.5.11
Java 21
Steps to reproduce
Create empty spring boot project, add following dependencies:
in the previous version, you could set it to false, and it would skip the init and it would all work, now it throws an exception that it doesn't exist
I would imagine that we who manage multiple collections, either create a constructor without creating any collection because if you don't specify the name, it puts the default one there. Or it doesn't throw an exception when init is set to false.
Expected behavior
Let us manage the collection creations, or when init set to false, don't create collection and don't throw exception breaking CDS image building
Minimal Complete Reproducible example
The example above and run the usual
Bug description
With latest version of 1.0.0-M3, even when using the base package for ChromaDB and manually initialising the collections, it's trying to create a collection messing up the Buildpacks and CDS.
Environment
Spring AI version 1.0.0-M3
Spring Boot version 3.3.4
ChromaDB version 0.5.11
Java 21
Steps to reproduce
Create empty spring boot project, add following dependencies:
Implement the Vectorstore beans and all that jazz
in the previous version, you could set it to false, and it would skip the init and it would all work, now it throws an exception that it doesn't exist
I would imagine that we who manage multiple collections, either create a constructor without creating any collection because if you don't specify the name, it puts the default one there. Or it doesn't throw an exception when init is set to false.
Expected behavior
Let us manage the collection creations, or when init set to false, don't create collection and don't throw exception breaking CDS image building
Minimal Complete Reproducible example
The example above and run the usual
with corresponding pom config
The text was updated successfully, but these errors were encountered: