Add a Chroma provider (CommunityToolkit.VectorData.Chroma)
维护者通常 1 天内回复
已经有一个关联 PR 被合并了。
- #58 来自 @Laurianti —— 已合并
评估
调研方向
Start by comparing the existing Qdrant provider structure in this repository with the reference implementation at ChromaDotNet/ChromaDB.VectorData. Then read the conformance-test requirements in the issue and the mevd.yml matrix; the requested additions are MEVD/src/Chroma, MEVD/test/Chroma.UnitTests, and MEVD/test/Chroma.ConformanceTests. Done means the provider and tests are included in the matrix and the conformance tests run against Chroma with Testcontainers.
由索引模型根据 Issue 内容生成。
描述
Summary
Add a Chroma provider for Microsoft.Extensions.VectorData as CommunityToolkit.VectorData.Chroma, in MEVD/src/Chroma with its unit and conformance tests, like the other providers of this repository.
Chroma is listed as planned for .NET in the vector store tables of Semantic Kernel and Agent Framework.
Background
In microsoft/semantic-kernel#12510, @roji wrote that a Chroma provider first needed an up-to-date low-level .NET client. ChromaDotNet.Client (repository) continues ChromaDB.Client and is tested against Chroma 0.4.10 to 1.5.9 and Chroma Cloud.
The provider
A working provider is at ChromaDotNet/ChromaDB.VectorData, published as ChromaDotNet.VectorData. It started as a copy of the Qdrant provider of this repository and keeps its structure.
- The Microsoft.Extensions.VectorData conformance tests pass against Chroma 1.5.0, 1.5.9 and the latest release, and on Chroma Cloud, hybrid search included. The test bases for multiple vectors and records without vectors are excluded: Chroma stores exactly one embedding per record.
- Limits that come from Chroma: metadata has no null values, so filtering on null is not supported;
GetAsyncwith a filter does not support ordering; comparisons work on numbers only.
Change
A pull request that adds MEVD/src/Chroma, MEVD/test/Chroma.UnitTests and MEVD/test/Chroma.ConformanceTests with the namespaces, package metadata and test layout of the other providers. The conformance tests start Chroma with Testcontainers, so the mevd.yml matrix runs them with the other providers.
Once CommunityToolkit.VectorData.Chroma is published, ChromaDotNet.VectorData is deprecated in its favor on NuGet. We keep maintaining the provider here.
- 主要语言
- C#
- 星标
- 8
- 派生
- 8
- 平均合并
- 1 天 8 小时
- 30 天内合并 PR
- 10
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
CommunityToolkit/AI 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 72/100
CommunityToolkit/AI#19 ·
维护者通常 1 天内回复
-
AzureDocumentDB: CosineDistance returns similarity scores, and ScoreThreshold filters the wrong way未关闭bug
难度 4/5 3-5 天 新手友好度 45/100
CommunityToolkit/AI#72 ·
维护者通常 1 天内回复
-
enhancement
难度 5/5 一周以上 新手友好度 35/100
CommunityToolkit/AI#61 ·
维护者通常 1 天内回复
-
enhancement
难度 5/5 一周以上 新手友好度 35/100
CommunityToolkit/AI#59 ·
维护者通常 1 天内回复
-
Report all Cosmos DB emulator issues可能重新可做 @adamsitnik 于 103 天前认领，目前没有进行中的 PR。 未关闭
CommunityToolkit/AI#23 · 已指派 1 人 ·
维护者通常 1 天内回复
查看 CommunityToolkit/AI 的全部 Issue
相似的 Issue
-
bug priority: P2
难度 1/5 1-3 小时 新手友好度 84/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 77/100
维护者通常 1 天内回复
-
[Docs] README/PRIVACY still name AppCenter although v1.5.6.0+ uses the Microsoft Store Services SDK未关闭
难度 2/5 1-3 小时 新手友好度 78/100
-
needs-triage
难度 2/5 1-3 小时 新手友好度 72/100
Azure/azure-sdk-tools#17317 ·
维护者通常 1 天内回复
-
Test
难度 2/5 1-3 小时 新手友好度 69/100
维护者通常 1 天内回复