Bug: Stop using v1 of Chroma API #10864

Activity

1. Dmitry Lukyanov (DmitryLukyanov)

   added

   bugSomething isn't workingSomething isn't working

   on Mar 9, 2025
2. Dmitry Lukyanov (DmitryLukyanov)

   added the

   Bug

   issue type on Mar 9, 2025
3. Mark Wallace (markwallace-microsoft)

   added

   triage

   on Mar 10, 2025
4. Sophia Lagerkrans-Pandey (sophialagerkranspandey)

   removed

   triage

   on Mar 10, 2025
5. Sophia Lagerkrans-Pandey (sophialagerkranspandey)

   assigned

   Mark Wallace (markwallace-microsoft)

   on Mar 10, 2025
6. Mark Wallace (markwallace-microsoft)

   added this to Semantic Kernelon Mar 10, 2025
7. Mark Wallace (markwallace-microsoft)

   moved this to Bug in Semantic Kernelon Mar 10, 2025
8. Mark Wallace (markwallace-microsoft)

   added

   memory connector

   memory

   msft.ext.vectordataRelated to Microsoft.Extensions.VectorDataRelated to Microsoft.Extensions.VectorData

   on Mar 10, 2025
9. Mark Wallace (markwallace-microsoft)

   added

   BuildFeatures planned for next Build conferenceFeatures planned for next Build conference

   on Mar 19, 2025
10. Mark Wallace (markwallace-microsoft)

    removed

    BuildFeatures planned for next Build conferenceFeatures planned for next Build conference

    on Mar 31, 2025
11. Mark Wallace (markwallace-microsoft)

    assigned

    westey (westey-m)

    and unassigned

    Mark Wallace (markwallace-microsoft)

    on May 15, 2025
12. Shay Rojansky (roji)

    marked Bug: Chroma API v2 not supported in Microsoft.SemanticKernel.Connectors.Chroma #12284 as a duplicate of this issue on Jun 17, 2025
13. roji commented on Jun 17, 2025

    

    Shay Rojansky (roji)

    on Jun 17, 2025

    Member

    More actions

    Note that if/when we do more work on Chroma support, it'll like be in the form of creating an implementation of the new IVectorStore implementation, rather than updating the current older IMemoryStore implementation; this is tracked by #12510.
14. westey (westey-m)

    added

    needs helpThese are issues that are good candidates for the community to work onThese are issues that are good candidates for the community to work on

    on Jun 19, 2025
15. github-actions commented on Jul 11, 2026

    

    github-actionsBot

    on Jul 11, 2026 – with GitHub Actions

    Contributor

    More actions

    This issue is stale because it has been open for 90 days with no activity.
16. github-actions

    added

    staleIssue is stale because it has been open for a while and has no activityIssue is stale because it has been open for a while and has no activity

    on Jul 11, 2026
17. rehan243 commented on Jul 12, 2026

    

    Rehan Malik (rehan243)

    on Jul 12, 2026

    More actions

    I ran into a similar issue with Chroma's API change recently, took me a few tries to figure out what was going on. The thing is, when I updated to the latest Chroma docker image, I started getting 400 responses too. I've been using Microsoft.SemanticKernel.Connectors.Chroma v1.40.0-alpha, same as you, and it looks like it's still using the old v1 API. I'd suggest bumping the connector version or patching it to use the new API, maybe by updating the API endpoint or request format to match what's expected by Chroma's latest version. I've seen some discussions on the Chroma repo about breaking changes, so it's probably worth digging into that issue you linked for more context.
18. github-actions

    removed

    staleIssue is stale because it has been open for a while and has no activityIssue is stale because it has been open for a while and has no activity

    on Jul 13, 2026
19. Laurianti commented on Oct 14, 2026

    

    Federico Laurianti (Laurianti)

    on Oct 14, 2026

    Contributor

    More actions

    #14579 removed the .NET Chroma connector. The Microsoft.Extensions.VectorData implementation for Chroma mentioned above is now CommunityToolkit.VectorData.Chroma, in CommunityToolkit/AI, and it uses the v2 API of Chroma.
20. westey-m commented on Oct 14, 2026

    

    westey (westey-m)

    on Oct 14, 2026

    Contributor

    More actions

    Thanks for the pointer Federico Laurianti (@Laurianti). Closing this issue.

    🚀React with 🚀1Reacted by Federico Laurianti
21. westey (westey-m)

    closed this as completedon Oct 14, 2026