Repository navigation
ChromaDotNet.Client and ChromaDotNet.Client.DependencyInjection 2.11.0, released together.
New
ChromaConfigurationOptions.WithChromaCloud()says the server is Chroma Cloud behind a proxy or another address, for the rules of Chroma Cloud.
Changes of behavior
- A record without metadata keys comes back with an empty
Metadata, not null, when the read includes the metadatas. AddAsync,UpdateAsyncandUpsertAsyncthrow anArgumentExceptionfor a metadata without keys and for a list of values of more than one type, as the Python client does.GetAsyncthrows anArgumentOutOfRangeExceptionfor a negative limit or offset, and returns no record for a limit of 0 without a request.- A write that fails after some of its batches went says how many records went, and a collection client made by name does not run it again.
- With
deleteRecordsFirst, records that the server returns after their delete make the client throw aChromaExceptionand keep the collection. ChromaQuery.NResultsrejects a negative number.
Fixes
- An id condition sends each id once.
CreateCollectionAsyncandGetOrCreateCollectionAsyncreject the names.and...- A connection string takes
httpandhttpsendpoints only. - The weight of the text in
ChromaRank.HybridRrfnever goes below 0. AddKeyedChromaClientgives each key its ownHttpClient, and a null key throws anArgumentNullException.
NuGet: https://www.nuget.org/packages/ChromaDotNet.Client/2.11.0 and https://www.nuget.org/packages/ChromaDotNet.Client.DependencyInjection/2.11.0