Apache Solr 10.0.0 was released on 3 March 2026. It is a real release with real engineering in it, and for website search it changes almost nothing you or your visitors would notice. Here is what Solr 10.0 adds, what it removes, why it leaves search relevance exactly where it was, why Opensolr waits for a mature 10.x release before adding it to the platform, and how to run Solr 10 today if your project needs it.
Solr 10.0 in one picture. The top half is what changed upstream. The bottom half is what your visitors actually use.
01 · WHAT SOLR 10.0 ACTUALLY ADDS
The Solr 10 upgrade notes group the changes into three areas. Most of them live below the surface your application talks to.
A newer runtime
Solr 10 requires Java 21 and runs on Jetty 12 and Lucene 10. Tracing moved from OpenTracing to OpenTelemetry, and ZooKeeper access now goes through Apache Curator. This is maintenance of the platform underneath Solr, not new search behaviour.
Cheaper and faster vector lookups
New quantized vector field types store each vector in fewer bits, which cuts memory at some cost to accuracy. The kNN parser gains efSearchScaleFactor, an early termination strategy, lexically seeded graph exploration and ACORN filtering for filtered vector queries. GPU vector search is available through a pluggable codec. All of these make vector retrieval lighter. None of them decide which document ranks first.
Admin and tooling
An experimental new Admin UI ships alongside the existing one, and the command line tools accept a --credentials option for Basic Authentication.
02 · WHAT IT DOES NOT CHANGE: RELEVANCE
Good website search is decided by how keyword matching and vector matching are combined into one ranked list. Solr 10.0 does not add a way to do that. Keyword scores and vector scores still live on different scales, and simply adding them together still lets one side drown out the other.
That problem is solved on Opensolr today, on Solr 9.6, by the Opensolr hybrid query parser. It scores every candidate document on both sides, normalises the two scores so they can be compared, and blends them with a weight you control. The quantized vector types in Solr 10 point the other way: they trade a little vector precision for memory, which only pays off at a scale most websites never reach.
03 · WHAT A WEBSITE SEARCH ACTUALLY NEEDS
Most Drupal, WordPress and CMS sites ask their search for the same handful of things. Almost all of them have been part of Solr for well over a decade. Solr 10.0 does not add a single line to this table.
| What the site needs | Part of Solr since | On Opensolr with Solr 9.6 |
|---|---|---|
| Full-text search with relevance ranking | The first releases | Yes |
| Facets and filters | Solr 1.x | Yes |
| Highlighted snippets | Solr 1.x | Yes |
| Spellcheck, did you mean | Solr 1.x | Yes |
| Autocomplete suggestions | Solr 3.x | Yes |
| Search by meaning (dense vectors) | Solr 9.0 | Yes |
| Hybrid keyword and vector ranking | No built-in score fusion, including 10.0 | Yes, Opensolr hybrid parser |
| AI hints and RAG answers | Not in Apache Solr | Yes |
04 · WHY WE DO NOT SHIP X.0 RELEASES
Every major Solr release starts with a first version that the community then stabilises over the following months. We wait for a mature release of each major line before it joins the platform, as we did with Solr 8.6 and 8.11, and as we do with the Solr 9 line we run today. Solr 10 will join Opensolr the same way, once the 10.x line has proven itself in production.
This is not caution for its own sake. On 1 September 2026, six months after 10.0.0 shipped, the Solr developers proposed an urgent 10.0.1 for bugs they described as critical in 10.0: one that breaks a major area of existing functionality, one that can cause request failures, and several that cause silent data loss in cross data centre replication. That is the normal life of an x.0 release, and it is exactly the period we keep your index out of.
05 · WHAT BREAKS WHEN A CONFIGURATION MOVES TO SOLR 10
Solr 10 also removes things that working Solr 9 configurations still use. A configuration that boots today on 9.6 can refuse to load on 10.0 because of any of these.
| Component | In Solr 10 | What it means |
|---|---|---|
| <lib/> in solrconfig.xml | Removed | Per-core jar loading is gone. Every plugin jar has to be installed on the server itself |
| master/slave replication config | Removed | Only leader and follower terminology is accepted |
| wt=php, phps, python, ruby | Removed | Clients reading those formats have to switch to JSON |
| wt=xlsx | Removed | Export CSV and convert it outside Solr |
| CurrencyField, EnumField | Removed | Schemas must move to CurrencyFieldType and EnumFieldType |
| ExternalFileField, PreAnalyzedField | Removed | Fields using them have to be redesigned and reindexed |
| HDFS, analytics module, hadoop-auth | Removed | No replacement inside Solr |
| Java | Java 21 minimum | Custom plugins built for older Java need a rebuild and a retest |
The full list is in the official Major Changes in Solr 10 page. For what changed between Solr 8 and 9, see Solr 9 Features and What's New.
06 · NEED SOLR 10 TODAY?
If your project requires Solr 10.0 right now, we can provision it on a dedicated server, with the same management, monitoring and support as the rest of the platform. See Enterprise Solr Cloud or tell us what you need.
Start on Solr 9.6
Create an index on Solr 9.6 and get vector search, hybrid ranking and the AI features built on them, on a release line that has already proven itself. Need Solr 10 on your own server? Talk to us.
Create a free indexDedicated serversTalk to us