A Fresh Start? The Path Toward Apache Solr's v2 API
summary
Apache Solr admits its V2 HTTP API effort started in 2017 as a JSON-based translation layer over V1 that decays when V1 changes, so the project pivots to JAX-RS and generates OpenAPI specs. The codebase counts about 245 APIs, with about 41 improved by newly onboarded contributors after workshops and new-dev issues. V2 is marked experimental to allow breaking iterations, ~100–120 V2 endpoints still need conversion, and client generation and breaking-change checks are now automated.
AI-written summary · about
chapters (10)
- 0:00Introduction to Solr's v2 API
- 4:15Why Solr needs a new API
- 8:28Early attempts and failures of v2
- 12:39Switching to a new framework
- 17:57Experimental status of v2 APIs
- 21:03Restful API redesign efforts
- 24:13Enabling new contributors
- 27:44Current state and future plans
- 32:39Lessons learned from the project
- 34:45Q&A session
related talks
37mOSS Security: Lessons from 10+ Years at Apache Solr
10mFrom custom Solr to out-of-the-box OpenSearch
26mPast, Present, and Future of AsyncAPI
29mThe maintainability of open source code 20 years from today
35mOpensource API Tools to agile your apifirst strategy.
21mWorking in the Open...Search
36mWhat’s New in the OpenSearch Project and Ecosystem
06mSponsored Keynote: Foundation-Led Innovation: OpenSearch's Impact on Modern Data I...