Multiple issues how am I supposed to use this?

[cyberpwnn]

What happened?

1. Tried "latest", realized most of the endpoints are totally broken (i cant delete a collection or list it for example)
2. Attempt to use the dev version which is actually the latest, then realize that while v1 is merely deprecated, you cant even use it. Ok fine, we will try v2
3. Unable to list tenants, its just not an endpoint, like list db or list collections

How am I supposed to use this?

Versions

"latest" as of March 7th, both dev and the docker latest. I'm not getting an actual version for you because this issue is still unresolved.

Relevant log output

[tazarov]

hey @cyberpwnn, sorry to hear about your trouble. Let's figure out how to get your going with Chroma.

Assuming by your reference to API v1/v2 you are probably using Chroma in a client/server mode. Historically, mismatches of client/server has been the greatest frustration for community members and as Chroma moves fast keeping the balance between features and backward compatibility is not as easy as it sounds :).

First off what stack are you on? Python/JS or any of the other supported ones - https://docs.trychroma.com/docs/overview/introduction#language-clients.

Can you run this to check your server version (once your docker/k8s etc is up an running):

curl -v http://localhost:8000/api/v2/version

Note

Invoke-WebRequest -Uri "http://localhost:8000/api/v2/version" -Verbose for Windows

Once you figure out the version here's an easy way to understand what it supports:

• Get a 404 error from the above - you must be on version <0.5.16
• Versions >=0.5.16 to <=0.6.3 API v1 and v2 are supported, there are some bugs in V1 APIs introduced around 0.6.2
• Versions >=0.7.0 API v2 is the only supported API

Having figured out your server version adjust your client(s) version accordingly. For Python that is relatively straightforward as we always ensure that the client and server on the same version will be 100% API compatible. For JS we always release a new version of the client that is API-compatible, although we do not (yet) have a compatibility table for this. For other clients your mileage will vary.

Tip

Always pin your server versions to ensure your client's don't break if/when docker pulls a newer version of Chroma. Instead of using chromadb/chroma:latest switch to using chromadb/chroma:0.6.3 for example.