Release v0.2.7: Embedding batching/concurrency and type safety improvements #12
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This release adds configurable embedding batching and concurrency controls for improved ingestion performance, along with comprehensive type safety improvements across the codebase.
Changes
Features
embedMany()for batch text embeddings when supported by the provider, with configurable concurrency limits for both text and image embeddingsembeddingProcessingconfig: Configureconcurrency(default: 4) andbatchSize(default: 32) viaunrag.config.tsunderdefaults.embeddingorengine.embeddingProcessingType Safety Improvements
anytype assertions with properly-typed interfaces for external SDKs:DriveFile,DriveClient,AuthClient)QueryRowinterface for Drizzle storeAssetMetadataFieldsinterface andhasAssetMetadata()type guard for asset-derived chunk metadatamergeDeeputility to dedicated module with proper generic type signaturesrequireOptional()helper now requires explicit type parametersInternal
core-embedding-batching.test.tstest suite for batching behaviordeep-merge.tsutility withisRecord()type guardRelated PRs