Fix Qdrant cloud indexing: Add keyword index for 'type' field during #170
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.
Issue link: #144
Description
Fixes "Index required but not found for 'type' field" error on cloud-hosted Qdrant instances by adding proper keyword indexing for the 'type' payload field during collection creation.
Type of Change
Bug fix (non-breaking change which fixes an issue)
Related Issue(s)
Fixes #[HELP WANTED] Bug: Qdrant semantic search fails due to missing index for "type" field
Changes Made
Added payload_schema parameter to QdrantVectorConfiguration for payload index support
Updated collection creation to include keyword index for 'type' field
Removed manual post-creation index creation (now handled at collection init)
Testing
Test Commands:
uv run pytest tests/semantic_search/ -v
uv run pytest tests/ -v --tb=short
All tests pass: 63 passed, 18 skipped
Checklist
-[x] My code follows the code style of this project
-[x] Unit tests pass locally
-[x] New and existing functionality works
-[x] No breaking changes
Additional Context
This resolves the Qdrant cloud filtering issue by ensuring collections are created with proper keyword indexes from the start.