v1.38.1
📦 weaviateView on GitHub →
✨ 4 features🐛 16 fixes⚡ 1 deprecations🔧 4 symbols
Summary
This patch release focuses heavily on stability, performance, and bug fixes across backup, replication, and internal management systems. Notably, the replicated indices queue feature has been removed due to low usage.
Migration Steps
- If you relied on the replicated indices queue feature, note that it has been removed and you may need to adjust workflows.
✨ New Features
- Add environment variables to disable bucket access check.
- Enable asynchronous replication if effective replication factor (erf) is 1 and actual replication factor (arf) is greater than 1.
- Lazy loading for property lengths implemented for performance improvement.
- Schema recording is dropped from usage reporting.
🐛 Bug Fixes
- Backup operations now return HTTP 422 instead of 500 when the backend module is missing.
- Debug endpoints are disabled by default.
- Replication factor bounds are validated at startup.
- Handled missing boost properties and property type validation errors.
- Fixed a race condition during usage module startup.
- Extended token fetch retry budget.
- Fixed a goroutine leak when listing all S3 backups.
- Increased timeout for ObjectTTL test to account for multi-node cluster readiness delays.
- Fixed the shebang in tools/dev/run_dev_server.sh script.
- Reduced the number of goroutines spawned by the cyclemanager.
- Fixed MCP hybrid search returning objects without properties.
- Switched cycle manager to backoff when idle.
- Stabilized TestReadRepairDeleteOnConflict against node boot timing.
- Prevented timeout during shard halting in unrelated unit tests.
- Fixed incorrect authorization check for getting groups for a role.
- Fixed backup concurrency calculation.
Affected Symbols
⚡ Deprecations
- Gut the replicated indices queue feature due to lack of use.