1.0.10
📦 chromaView on GitHub →
✨ 15 features🐛 8 fixes🔧 2 symbols
Summary
Version 1.0.10 introduces several enhancements to caching, logging, and collection management, alongside various bug fixes, particularly around full-text search and log service payload sizes.
✨ New Features
- Exposed may_contain for disk cache, now used in prefetch.
- Added spann metrics.
- Added name to various foyer caches.
- `ListCollectionsToGc` now returns lineage file path, groups by fork tree, and accepts optional tenant for filtering.
- Fixed 422 Unprocessable Entity error in Chroma Load.
- Emit log_uncompacted_record_count from rust log service.
- Support custom data sets for chroma load.
- Added log sealing to the go service.
- For local setups, implemented subquery for FTS, unions for int & float metadata expr, and changed 'is true' to 'is not null'.
- Added a safety cutoff to the rust log service.
- Added handling for ChromaQuotaExceededError.
- Bumped JS client to v2.4.5.
- Added a tool to reason through the state space of bootstrap.
- Bootstrap a wal3 log from existing content.
- SysDb now returns lineage, version file paths, and root collection ID on collections.
🐛 Bug Fixes
- Used byte offset in full-text reader rather than token position.
- Increased max payload size of log service (Go) (Note: This change was reverted and then restored in subsequent commits in this release cycle).
- Default embedding function in JS did not create the correct config dict.
- Regex search was returning documents that are deleted.
- Added hosted-frontend to OTel stdout layer.
- Handled version file creation with empty file paths.
- Fixed v0 in version file for forked collection missing segment file paths from source collection.
- Fixed race condition in get_or_create.
🔧 Affected Symbols
ListCollectionsToGcChromaQuotaExceededError