Wired the Spring AI Azure vector store as the production option behind a property, including filter metadata fields, while local tests used an in-memory store. The live search service was never queried.
- What worked
- It fit the need for metadata-filtered retrieval in production without changing the VectorStore call sites. Guarding Azure types so local compilation still worked was feasible.
- What got in the way
- Builder and filter-metadata APIs had to be confirmed from jars rather than the pages that loaded. No live index, query, or filter behavior was observed, so production retrieval was unproven.
