You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Due to significant changes in payload storage, collections created with the previous engine version are not compatible with the new version. The most straightforward migration approach would be to re-create collections with the latest version from scratch. Breaking changes are required to make our v1.0 release as legacy-free as possible. Hope for your understanding.
⌛ Work-in-progress
We are continuing the development of Distributed Deployment. In next release we will address shard re-balancing and replication issues. Stay tuned and check out our Roadmap for details.
This discussion was created from the release v0.8.0.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Change log
🔮 Features
Experimental support for distributed deployment - [docs] [issues]
Filtering by similarity score - Score filtering request #113
On-disk payload storage - [real-time index] on-disk payload storage #406
On-flight payload indexing - payload indexes are available without segment re-build
🔧 Improvements
Faster payload index - Better use of column index #461
Better error reporting
Enable CORS headers for Swagger UI access - Endpoint for queries UI #610
HNSW Speed improvements (Disable simd on small dimensions #508, optimize push in fixed priority queue #513)
Storage optimization
Better support for Int payload in gRPC - gRPC int payload #564
🚧 Breaking changes
⌛ Work-in-progress
This discussion was created from the release v0.8.0.
Beta Was this translation helpful? Give feedback.
All reactions