Unconference Session: OpenSearch 4.0: What? When? Why?
summary
Proposes treating OpenSearch 4.0 as a policy decision not just a feature bump, separating three real breaking-change classes: API compatibility (avoid removing endpoints after long use; doc type removal was painful), runtime and plugin surface (raising minimum JVM to Java 25 to use virtual threads or foreign memory APIs), and Lucene data format where current n minus one support forces expensive re-indexing required migrations; suggests solving Lucene migration or loosening what counts as “breaking” to avoid disruptive major-version upgrades.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 1:05OpenSearch 4.0 timeline and SemVer
- 2:50Breaking changes in versions
- 6:44Major version necessity
- 9:54Breaking changes and Lucene limits
- 11:40Major version psychology
- 13:26Q&A on Lucene updates
related talks
09mUnconference: OpenSearch is not a database!
05mKeynote: OpenSearch: From Code to Community
06mSponsored Keynote: Foundation-Led Innovation: OpenSearch's Impact on Modern Data I...
24mReimagining Search : Scaling OpenSearch Across an Enterprise - Platform C...
45mAnything New in Search? What If I Find It?
41mDynamoDB, Neptune and OpenSearch: A Unified Approach to Collaborative Editing and Search #JSConfAM25
38mFree enterprise search with OpenSearch
18mSpeed Up Your Search: Concurrency and Merge Policies to the Rescue