Integrating database-specific features to Vectorstore

[anders-swanson]

I’ve been playing around with Spring AI’s VectorStore interface, and feel like it abstracts away too much of the specific backing database for more complex use cases, especially when using advanced RDBMS features.

For example, if I want to wrap a vector similarity search and an INSERT into a separate table in a single database transaction, it doesn't seem possible with the current interface due to a lack of transactional control or schema relationships.

Is there a recommended way to extend VectorStore for database-specific control? I couple implement a custom version and bypass the interface entirely, but would prefer some form of extensibility if it's planned.