Skip to main content
XenonStack

Big Data Engineering

XenonStack Blog Apache Solr: Architecture, Vector Search and Solr 10

| Published | Updated

Apache Solr: Architecture, Vector Search and Solr 10
14:04

Key takeaway

  • Apache Solr in 2027: architecture, SolrCloud, vector and hybrid search, security and Solr 10.1 changes, with when to choose Solr and how to deploy it.

Apache Solr is an open source search platform built on Apache Lucene that provides full-text, vector and geospatial search over large document collections. It indexes documents made of fields, answers queries over HTTP, and scales out through SolrCloud, which adds distributed indexing, replication, load-balanced querying, automated failover and centralised configuration.

Solr 10.1.0, released on 27 October 2026, is the current release. The 10.x line needs Java 21, runs on Lucene 10.4, removes several legacy modules and adds hybrid search that blends keyword and vector results. This guide covers how Solr works, what changed in Solr 10, how to secure and deploy it, and when another engine is the better fit.

What is Apache Solr?

The Solr project describes Solr as an open source, multi-modal search platform that draws on Lucene's full-text, vector and geospatial search capabilities. Its feature areas include faceting, statistics and aggregations, spatial search, rich content handling, plugins and scaling with SolrCloud.

Everything Solr searches is a document: a set of named fields, usually with a unique ID that acts like a primary key. When a field is defined in the schema, Solr applies that field's analysis steps when the content is tokenised. According to the indexing guide, content usually arrives through Solr Cell with Apache Tika for binary files, through HTTP uploads of XML files, or through Java applications using the client API.

How does the Apache Solr architecture work?

A request to Solr passes through a small set of pluggable components. Knowing them helps architects decide where custom logic belongs.

ComponentWhat it doesTypical use
Request handlerReceives an HTTP request and decides how to process itSeparate endpoints for search, updates and administration
Query parserTurns query text into a Lucene query and checks its syntaxKeyword, structured or knn vector queries
Search componentsAdd features to a search requestFaceting, highlighting, spell checking
Analysers and tokenisersBreak field text into tokens and normalise themLanguage handling, stemming, synonyms
Update request processorsChange documents as they are indexedAdding, removing or transforming fields
Response writersFormat results for the callerJSON or XML responses to applications

SolrCloud or user-managed mode?

Solr runs in one of two cluster modes. Most enterprise deployments choose SolrCloud.

QuestionSolrCloudUser-managed
Who coordinates the cluster?ZooKeeper tracks nodes and core state and stores configurationYou, manually or with local scripts
How is data split?Collections are sharded automatically on creationYou create shards and route documents yourself
What happens if a leader fails?Another replica is elected automaticallyNo built-in failover; you edit solrconfig.xml and reload cores
When it fitsProduction clusters that need resilience and scaleSmall, single-node or legacy leader and follower setups

What has changed in Solr 10?

Solr 10.0.0 was released on 3 March 2026 and Solr 10.1.0 on 27 October 2026, according to the Solr news page. The changes below matter most when upgrading from older guides, which often still show Solr 7 or 8 on Java 8.

Two-column diagram: Java 8 to Java 21, local Tika engine to Tika Server, Kerberos via hadoop-auth to JWT or certificate authentication, keyword-only search to hybrid search with reciprocal rank fusion.
AreaEarlier positionSolr 10 position
JavaJava 8 in older guides, including the Solr 7.2 install steps this post used to showJava 21 for the server, Java 17 for SolrJ
Lucene and web stackOlder Lucene and Jetty releasesLucene 10.4, Jetty 12 and Jakarta EE 10 in Solr 10.1
Rich document extractionEmbedded local Tika engineRemoved; run a Tika Server and set tikaserver.url
Modulesanalytics, hadoop-auth and jaegertracer-configurator modulesAll three removed in Solr 10.0
Field typesExternalFileField, CurrencyField and EnumFieldRemoved in Solr 10.0
JWT authenticationblockUnknown defaulted to false in codeDefaults to true in Solr 9.11 and 10.1, blocking unauthenticated requests
SearchKeyword search with separate vector queriesHybrid search through reciprocal rank fusion and nested vector search in 10.1
Admin UIClassic Admin UI onlyExperimental new Admin UI at /solr/ui alongside the classic one

Solr 9.11.0, released on 4 October 2026, is the last 9.x release. The downloads page says the previous major version may receive critical bug fixes only, so new projects should start on 10.x.

How does Solr handle vector and hybrid search?

Solr stores embeddings in a DenseVectorField and searches them with the knn query parser. The dense vector search guide sets HNSW, the approximate nearest neighbour graph implemented in Lucene, as the default algorithm, with euclidean, cosine and dot product similarity. A knn query returns 10 neighbours unless you set topK.

Three further options affect cost and design. Scalar and binary quantised vector fields reduce memory use by storing smaller values per dimension. The experimental knn_text_to_vector parser, which uses LangChain4j, encodes query text with a model registered in Solr. Solr 10.0 added a cuVS-Lucene codec for GPU acceleration, though the 10.1 guide notes that GPU vector indexing does not work in that release. Solr 10.1 then adds hybrid search through reciprocal rank fusion, which merges keyword and vector rankings.

For retrieval behind AI agents, the search index is only one layer. ElixirData AgentSearch provides context-aware enterprise search across unstructured knowledge bases, with access controls and governance applied from ElixirData Context OS, which keeps governed context, versioned policy and decision traces in one decision layer above AI agents.

How should you secure Apache Solr?

Solr security is configured in a security.json file. In SolrCloud it lives at the ZooKeeper chroot and is uploaded with bin/solr zk cp; in standalone mode it sits in $SOLR_HOME. The authentication and authorisation guide lists these plugins:

ControlCurrent optionsWhat to check
AuthenticationBasic, JWT and Certificate authentication pluginsSet JWT blockUnknown to true explicitly on releases before 9.11 and 10.1
AuthorisationRule-based and external role rule-based authorisation pluginsPatch for CVE-2026-22022, a RuleBasedAuthorizationPlugin bypass affecting 5.3.0 to 9.10.0
Core creationFile-access checks in standalone core creationPatch for CVE-2026-22444, affecting 8.6 to 9.10.0
AuditAudit logging section in security.jsonSend audit events to your security monitoring
NetworkTLS between clients and nodes, ZooKeeper access controlKeep Solr and ZooKeeper off the public internet

Kerberos is not in the current plugin list, and Solr 10.0 removed the hadoop-auth module. If your clusters still use Kerberos, as described in our deep dive into Apache Solr security, plan the move to JWT or certificate authentication before upgrading.

How should enterprises deploy Solr going into 2027?

Older guides install Solr by hand on a single virtual machine with Java 8. For current releases, follow this sequence.

  1. Define the search problem. Keyword, faceted, vector or hybrid; document volume; freshness needed; who may see which results.
  2. Start on Solr 10.1 with Java 21. Do not start new work on 9.x, which is in critical-fix-only mode.
  3. Choose SolrCloud. Run a dedicated ZooKeeper ensemble for production clusters and keep it under the same change control as Solr.
  4. Run on Kubernetes with the Solr Operator. The Apache Solr Operator is built to manage Solr on Kubernetes and deploy SolrCloud; v0.9.1 was announced on 25 March 2025.
  5. Secure before loading data. Enable authentication, rule-based authorisation, TLS and audit logging in security.json.
  6. Plan extraction. If you index PDFs or Office files, run a separate Tika Server, because the local Tika engine is gone.
  7. Test relevance and capacity. Measure query latency, index size with and without vector quantisation, and recovery after node loss.

If you would rather not run the cluster yourself, see Managed Apache Solr Services. Teams pairing Solr with a wide-column store for source data can read our guide to implementing Apache Cassandra on AWS.

When should you choose Solr, and when not?

SituationFitReason
You need an Apache Software Foundation project with community governanceSolrSolr is developed at the ASF; Elasticsearch is offered under SSPL 1.0, AGPLv3 and the Elastic License 2.0, with default distributions under the Elastic License 2.0
Faceted catalogue or site search over structured fieldsSolrFaceting, statistics and schema-driven analysis are core features
Hybrid keyword and vector retrieval for AI applicationsSolr 10.1 or a dedicated vector storeSolr 10.1 adds reciprocal rank fusion; test recall and latency against your embeddings
Log analytics and observability dashboardsUsually another toolTeams often choose a stack built around log ingestion and dashboards
A small app with a few thousand recordsDatabase full-text searchA separate search cluster adds operational cost

Elastic added AGPLv3 as a licence option in September 2024, according to its licensing FAQ. Check the licence of the exact distribution you deploy, not only the source code.

To map one search-driven decision your agents should make, and the context and policy it depends on, book a Context Workshop. See what happens in the workshop.

What should you plan for in 2027?

Solr 10.1 is the release to build on, so plan around it rather than around older guides. Three points from this guide shape the year.

  • Start new work on Solr 10.1 with Java 21. Version 9.x is in critical fix only mode, so new projects gain nothing by starting there.
  • Settle security before upgrading. If clusters still use Kerberos, plan the move to JWT or certificate authentication, set JWT blockUnknown explicitly on older releases and patch the authorisation and core creation issues listed above.
  • Plan extraction and retrieval. Run a separate Tika Server for PDFs and Office files, and test relevance, latency and recall before you rely on hybrid keyword and vector search.

Measure query latency, index size and recovery after node loss before each rollout.

Frequently asked questions about Apache Solr

What is the latest version of Apache Solr?

Solr 10.1.0, released on 27 October 2026, is the current release. Solr 9.11.0, released on 4 October 2026, is the last release in the 9.x series and may receive only critical bug fixes.

Which Java version does Solr 10 need?

Solr 10 needs Java 21 for the Solr server and Java 17 for the SolrJ client library.

Does Apache Solr support vector search?

Yes. Solr stores embeddings in DenseVectorField, searches them with the knn query parser using an HNSW graph by default, and supports euclidean, cosine and dot product similarity. Solr 10.1 adds hybrid search through reciprocal rank fusion and nested vector search.

What is the difference between SolrCloud and user-managed Solr?

SolrCloud uses ZooKeeper to track nodes, store configuration, route requests and elect a new leader when one fails. In user-managed mode, sharding, routing, load balancing and failover are left to you.

Is Kerberos authentication still available in Solr?

The current Solr Reference Guide lists Basic, JWT and Certificate authentication plugins, and Kerberos is not among them. Solr 10.0 also removed the hadoop-auth module, so plan JWT or certificate authentication for new clusters.

Next Steps with Apache Solr Search Engine

Talk to our experts about implementing compound AI system, How Industries and different departments use Agentic Workflows and Decision Intelligence to Become Decision Centric. Utilizes AI to automate and optimize IT support and operations, improving efficiency and responsiveness.

Follow XenonStack on LinkedIn: XenonStack on LinkedIn for new guides on agentic AI, data and platform engineering.

Ready to put AI agents to work? Explore ElixirClaw, the agentic OS platform to build, orchestrate and govern AI agents.

Table of Contents

navdeep-singh-gill

Navdeep Singh Gill

Global CEO and Founder of XenonStack

LinkedIn profile

Navdeep Singh Gill is serving as Chief Executive Officer and Product Architect at XenonStack. He holds expertise in building SaaS Platform for Decentralised Big Data management and Governance, AI Marketplace for Operationalising and Scaling. His incredible experience in AI Technologies and Big Data Engineering thrills him to write about different use cases and its approach to solutions.

Get the latest articles in your inbox

Subscribe Now

Interested in solving your challenges with the XenonStack team?
Get Started

Tell us about you and your priorities so we can prepare the right conversation. It takes about 2 minutes.

Please Select your Industry
Banking
Fintech
Payment Providers
Wealth Management
Discrete Manufacturing
Semiconductor
Machinery Manufacturing / Automation
Appliances / Electrical / Electronics
Elevator Manufacturing
Defense & Space Manufacturing
Computers & Electronics / Industrial Machinery
Motor Vehicle Manufacturing
Food and Beverages
Distillery & Wines
Beverages
Shipping
Logistics
Mobility (EV / Public Transport)
Energy & Utilities
Hospitality
Digital Gaming Platforms
SportsTech with AI
Public Safety - Explosives
Public Safety - Firefighting
Public Safety - Surveillance
Public Safety - Others
Media Platforms
City Operations
Airlines & Aviation
Defense Warfare & Drones
Robotics Engineering
Drones Manufacturing
AI Labs for Colleges
AI MSP / Quantum / AGI Institutes
Retail Apparel and Fashion

Continue