Chroma DB default tenant and database : should be able to ovverride through application properties

[AmritSDutta]

chromaDb usually keeps it as default_tenant and default_database, for the tenant and database.
This should be the same in Spring AI.

Otherwise, allow overriding through application properties. Like -
spring.ai.vectorstore.chroma.client.tenant=default_tenant
spring.ai.vectorstore.chroma.client.database=default_database

Current Behavior

At present,
public static final String DEFAULT_TENANT_NAME = "SpringAiTenant";
public static final String DEFAULT_DATABASE_NAME = "SpringAiDatabase";

not able to override through application properties.
Even the logs are misleading somehow-
log:
Collection <collection_name> doesn't exist and won't be created as the initializeSchema is set to false.

Log does not mention the tenant or database under which it is trying to search the collection.

Context

[sunyuhan1998]

May I ask what version of Spring AI you are using? PR: #3435 seems to have fixed this issue.

[AmritSDutta]

'springAiVersion', "1.0.0"

Not sure what is fixed . Is it possible to override like following?

spring.ai.vectorstore.chroma.database-name=default_database
spring.ai.vectorstore.chroma.tenant-name=default_tenant

[sunyuhan1998]

'springAiVersion', "1.0.0"

Not sure what is fixed . Is it possible to override like following?

spring.ai.vectorstore.chroma.database-name=default_database spring.ai.vectorstore.chroma.tenant-name=default_tenant

I think this PR fixes the issue you are talking about, but it should not be included in the Spring AI 1.0.0 GA version, maybe you could err on the side of upgrading to the latest 1.1.0-SNAPSHOT version!

[AmritSDutta]

Thanks for clarifying. Verified with 1.1.0-SNAPSHOT. 👍

At the same time,
Log does not mention the tenant or database under which it is trying to search the collection. I guess it would be beneficial to mention the tenant database considered for the logs.

Collection <collection_name> doesn't exist and won't be created as the initializeSchema is set to false.

[ilayaperumalg]

Thanks @sunyuhan1998 for the original fix to this issue. Also, Pushed the commit to have a better logging via 0d8eebd.