[BUGFIX] Move vector search config inside search { } block - #78
Open
dkd-dobberkau wants to merge 1 commit into
Open
[BUGFIX] Move vector search config inside search { } block#78dkd-dobberkau wants to merge 1 commit into
dkd-dobberkau wants to merge 1 commit into
Conversation
The vectorSearch settings were placed outside the search { } block, which
made TypoScript resolve them to plugin.tx_solr.query.type and
plugin.tx_solr.vectorSearch.* — but EXT:solr reads from
plugin.tx_solr.search.query.type. As a result, vector search was
silently disabled in the demo site:
* TypoScriptConfiguration::isVectorSearchEnabled() returned false
* AbstractIndexer never set vectorContent on documents
* SolrWriteService never appended update.chain=textToVector
* No embeddings were produced during indexing
Move the three keys inside the search { } block so EXT:solr picks them
up correctly and the demo actually exercises the vector pipeline.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
dkd-kaehm
force-pushed
the
main
branch
2 times, most recently
from
May 20, 2026 20:53
3692419 to
9db01db
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
The vector search configuration in this demo sitepackage is silently disabled
because the three keys live one level too high in the TypoScript hierarchy.
The current setup writes:
plugin.tx_solr.query.type = 1plugin.tx_solr.vectorSearch.minimumSimilarity = 0.75plugin.tx_solr.vectorSearch.topK = 1000…but EXT:solr reads:
plugin.tx_solr.search.query.type(TypoScriptConfiguration::getSearchQueryType())plugin.tx_solr.search.vectorSearch.minimumSimilarity(getMinimumVectorSimilarity())plugin.tx_solr.search.vectorSearch.topK(getTopKClosestVectorLimit())So
isVectorSearchEnabled()always returnsfalseon this demo site:AbstractIndexernever copiescontent→vectorContentSolrWriteService::addDocuments()never appendsupdate.chain=textToVectorThis patch moves the three keys inside the existing
search { }block soEXT:solr picks them up and the demo actually exercises the vector pipeline
that landed in 13.1 / EXT:solr 14.
Reproduction (before the fix)
With Solr 10 +
language-modelsmodule + a registered LLM in the model store(e.g. local Ollama with
nomic-embed-textvia OpenAI-compatible endpoint):ddev exec "vendor/bin/typo3 scheduler:execute --task=2"Reports → Status → Apache Solr Text to Vectorshows model present, but nodocument ever gets a vector
After the fix:
for 58 docs in
core_en)/content-examples/form-elements/search?q=…returnssemantically related hits even when the query has no keyword overlap with
any title (verified locally on EXT:solr 14.0.0-beta1).
Test plan
ddev startllmmodel in the Solr model storeForce Re-Indexingtask or Index Queue Worker🤖 Generated with Claude Code