SCORE Lexical Search
High-speed, fuzzy autocomplete and exact match search powered by Apache Solr.
SCORE Lexical Search indexes content, media, and taxonomy into unified Apache Solr cores. Using the Search API, STD.DEV enables direct HTTP/REST querying from Genkit or frontends, offering lightning-fast exact text resolution, URL routing, and fallback autocomplete suggestions without requiring full Drupal bootstraps.
High-Speed Indexing
Powered by Apache Solr, the lexical search engine continuously indexes content, media, and taxonomy terms into highly optimized cores. This ensures that massive datasets remain instantly searchable with exact-match precision and advanced fuzzy logic.
Autocomplete & URL Routing
The service provides lightning-fast autocomplete suggestions for frontends without requiring a full Drupal bootstrap. Additionally, it can directly resolve lexical queries into exact URL routes, drastically reducing time-to-first-byte (TTFB) for search navigations.
Headless REST APIs
Exposed seamlessly through the Drupal Search API, the Solr engine provides secure HTTP/REST endpoints. This allows any decoupled client application to execute complex search parameters and aggregations autonomously.
Deterministic AI Routing
Lexical Search is exposed as a primary tool for the SCORE Genkit microservice. The AI agent dynamically evaluates user intent, actively choosing to route queries to Solr when a task requires precise, deterministic keyword and entity matching rather than broad semantic similarity.
What technology powers the SCORE Lexical Search indexing?
SCORE Lexical Search is powered by Apache Solr for indexing content, media, and taxonomy into unified cores.
How does SCORE Lexical Search enable fast querying from external applications?
What are the benefits of using Apache Solr for the lexical search engine?
How does the autocomplete feature improve frontend performance?
Can SCORE Lexical Search directly map search queries to specific URLs?
What kind of API access does the Solr engine provide for decoupled applications?
How does SCORE Genkit utilize Lexical Search for AI agents?
When does the AI agent choose to route queries to Solr instead of using semantic similarity?
What is the primary purpose of SCORE Lexical Search?
What kind of search capabilities does SCORE Lexical Search offer beyond exact matches?
What is the advantage of not requiring a full Drupal bootstrap for autocomplete?
How does SCORE Lexical Search reduce Time-To-First-Byte (TTFB)?
What does SCORE Lexical Search index into Apache Solr cores?
What are the key features of SCORE Lexical Search?
How does the system handle large amounts of data for searchability?