Managing Custom Plugins and Forks of Solr
summary
Guidance for maintaining Solr plugins and forks that actually helps: use Lucene and Solr test artifacts (Lucene Test Framework, SolrTestCaseBase), write tests that run against EmbeddedSolrServer, MiniSolrCloudCluster and HTTP-mode (Jetty) or Docker via testcontainers so the same test validates multiple modes; add randomized, seedable tests to catch edge cases; avoid long-lived divergent forks—cherry-pick and keep changes minimal; version plugin artifacts by Solr version (eg 8.6-pluginname-1.0), and mount built jars into Docker for fast local iteration.
AI-written summary · about
chapters (6)
- 0:00Introduction and context
- 4:17Testing strategies
- 14:33Randomized testing
- 22:08Managing project forks
- 27:34Composition and management
- 36:25Q&A and closing
related talks
29mThe maintainability of open source code 20 years from today
24mExtending OpenSearch: A Practical Guide To Building Custom Plugins
29mPlan to fork (So you don't have to fork)
50mSplitting component containers to simplify dependencies
32mA Fork to Reckon With: Minimizing Friction When Adopting OSS
37mA Deep Dive Into OpenSearch Plugin Architecture and Introducing Hot...
43mSpinnaker Plugins: Extending...
47mWhy your shared libraries are ill - and how to cure them