chore: drop bleve configuration - #190
brandon1024 wants to merge 1 commit into
Conversation
The experimental bleve search features have been removed since v11.x. Enterprise customers should use a proper search backend like ElasticSearch, and smaller deployments should use database search (enabled by default). Drop bleve configuration.
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (2)
💤 Files with no reviewable changes (2)
Included review availability: Your plan provides up to 4 included reviews per hour; 3 remain after this review. 📝 WalkthroughWalkthroughThe Mattermost Compose service no longer mounts a Bleve index directory or sets its container path. The example environment template also no longer lists the related variables or explanatory comment. ChangesBleve configuration removal
Priority: ⬇️ Low Estimated code review effort: 1 (Trivial) | ~3 minutes Change: Other Merge Risk: ⚪ Minimal · up to No actionable merge risk is established for this configuration removal; it is mergeable after normal checks. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Summary
The experimental bleve search features have been removed since v11.x. Enterprise customers should use a proper search backend like ElasticSearch, and smaller deployments should use database search (enabled by default).
Drop bleve configuration.
Ticket Link
None.