Hi all, Sorry for the delay, I forgot to do the notes for our last meeting. Here they are. Please don't hesitate to reply if I missed something or if there are errors.
Regards, Serge... Attendees: • Jonathan Sinovassin-Naïk • Serge Huber • Jérôme Blanchard • Francois Gerthoffert Below is the summary of the discussions held during the meeting. ⸻ 1. Elasticsearch 9 Migration & Release Planning The team discussed the status of the ongoing migration to Elasticsearch 9 [1]: • On-premise tests with Elasticsearch 9 are complete and behave correctly. • Migration tests using Elastic Cloud [2] are planned before the end of the month. • The tentative target for the 3.0 release is early to mid-November, depending on migration test results. • Elasticsearch 7 will reach end-of-life on January 15, 2026, so customer environments should be migrated beforehand. • Performance tests on existing implementations show comparable results with no regressions. The new Elasticsearch Java client runs correctly on Apache Karaf [3]. ⸻ 2. Technical Updates OpenSearch Branch Work continues on the OpenSearch compatibility branch [4]: • Updates are ongoing to align with recent Karaf and Elasticsearch 9 changes. • Some complexities arise due to interactions between older Elasticsearch logic and new changes. • Unrelated content is being removed from the branch to simplify maintenance. • A ticket was opened in the Apache Karaf project to handle configuration issues introduced by the plugin. Past Event Condition Builder A circular dependency issue exists between the service and search layers. This will require additional design work once the Elasticsearch 9 migration stabilizes. Manual Documentation Deployment The documentation system was improved: • Both the stable and snapshot manuals are now deployed. • Scripts were updated to retain only the two most recent versions. • Release documentation was updated accordingly. ⸻ 3. Scheduler & Annotation Discussions Annotation-Based Scheduler Jérôme presented an approach for defining scheduled jobs using annotations. This could simplify integration testing and multi-node deployment. The system would build on top of the existing scheduler rather than using external options like Quartz [5]. This topic will be revisited after the 3.0 release. Cache System Discussion Jérôme introduced an annotation-based cache system concept inspired by J2EE [6] and Jakarta EE [7]. Concerns were raised regarding long-term maintainability of introducing additional caching infrastructure. The concept will be discussed further, potentially with input from Kevan Jahanshahi. Blueprint → Declarative Services (DS) Conversion Serge experimented with converting OSGi Blueprint [8] to OSGi Declarative Services (DS) [9] using a Maven plugin. The work was paused due to complexity and because it is not appropriate for inclusion in the 3.0 release. ⸻ 4. Dependency Cleanup & Future Considerations • CXF usage has been reduced significantly; approx. 10% of APIs still depend on CXF [10]. Further isolation and eventual removal were identified as long-term goals. • Future evaluations include upgrading to Apache Karaf 4.4.9 or 4.5.x once the 3.0 release is complete. ⸻ 5. Apache Trusted Release Platform The team also discussed the Apache Trusted Release Platform [11], which automates license verification and provides tooling to support the ASF release workflow. It will continue to be evaluated for potential use in future releases. ⸻ References [1] Elasticsearch, https://www.elastic.co/elasticsearch/ [2] Elastic Cloud, https://www.elastic.co/cloud/ [3] Apache Karaf, https://karaf.apache.org/ [4] OpenSearch, https://opensearch.org/ [5] Quartz Scheduler, https://www.quartz-scheduler.org/ [6] J2EE, https://www.oracle.com/java/technologies/java-ee-glance.html [7] Jakarta EE, https://jakarta.ee/ [8] OSGi Blueprint, https://www.osgi.org/specification/osgi-blueprint/ [9] OSGi Declarative Services, https://www.osgi.org/specification/osgi-cmpn/ [10] Apache CXF, https://cxf.apache.org/ [11] Apache Trusted Release Platform, https://tooling.apache.org/platform.html
