feat(spring-ai-azure-store): Add support for configurable field names… #4989
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… in Azure Vector Store, allowing users to work with existing Azure AI Search indexes that use custom field names instead of the hardcoded defaults (`content`, `embedding`, `metadata`). ## Motivation - Problem Azure AI Search indexes may use custom field names (e.g., `chunk_text` instead of `content`). Currently, `AzureVectorStore` hardcodes field names, making it incompatible with such indexes. Without this feature, users must use native Azure SDK directly (bypassing Spring AI abstractions) Following the pattern established by `PineconeVectorStore`, which already supports custom field names. Signed-off-by: Alexandros Pappas <apappascs@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
… in Azure Vector Store, allowing users to work with existing Azure AI Search indexes that use custom field names instead of the hardcoded defaults (
content,embedding,metadata).Motivation - Problem
Azure AI Search indexes may use custom field names (e.g.,
chunk_textinstead ofcontent). Currently,AzureVectorStorehardcodes field names, making it incompatible with such indexes.Without this feature, users must use native Azure SDK directly (bypassing Spring AI abstractions) Following the pattern established by
PineconeVectorStore, which already supports custom field names.Thank you for taking time to contribute this pull request!
You might have already read the contributor guide, but as a reminder, please make sure to:
git commit -s) per the DCOmainbranch and squash your commitsFor more details, please check the contributor guide.
Thank you upfront!