Skip to content

Conversation

@destiny3912
Copy link

@destiny3912 destiny3912 commented Jan 15, 2026

Description

This Pull Request changes the content field name of the Qdrant Vector Store to enable setting via auto configuration in hard-coded "doc_contents"
fix #3797

Changes

  • Add contentFieldName in QdrantVecotrStoreProperties

Usage

Add property spring.ai.vectorstore.qdrant.content-field-name to application.yml

@ilayaperumalg ilayaperumalg self-assigned this Jan 15, 2026
metadata.put(DocumentMetadata.DISTANCE.value(), 1 - point.getScore());

var content = (String) metadata.remove(CONTENT_FIELD_NAME);
var content = (String) metadata.remove(DEFAULT_CONTENT_FIELD_NAME);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Now that the content field name is configurable, we should be using the content field name instead of the default one.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for the feedback. The intention was to handle null safety when contentFieldName was not configured, but it was wrong. It will be corrected

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@destiny3912 Are you planning to update the PR to fix this? or, do you want me to handle when merging? Thank you

Copy link
Author

@destiny3912 destiny3912 Jan 17, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ilayaperumalg I fix it now, please check it, Thank you

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Feature Request: Allow configuration of payload content key for QdrantVectorStore

2 participants