IAddon for the Chroma vector database backend.
On initialize! it configures the Chroma connection, builds a
ChromaMemoryStore, connects it and registers it in the hive-spi memory
registry: under :registry-key (default :chroma), and as the ACTIVE
store only when no other backend holds that slot (an addon never evicts
another backend; :active? true in the config forces it, which is what a
deployment whose :services :memory-store :backend is chroma wants).
It also offers Chroma as the host's IVectorCollectionStore, again only when none is installed yet (hive-chroma.host/install-vector-store!).
Config (manifest :addon/config, overridden by the init config): :host :port :collection-name the Chroma endpoint (defaults CHROMA_HOST / CHROMA_PORT env, then localhost:8000, hive-mcp-memory) :registry-key registry slot, default :chroma :active? claim the :default slot even when taken :vector-store? offer the vector-collection port, default true
No namespace here requires the host: everything host-side goes through hive-chroma.host, i.e. through hive-spi's host-services registry, so this loads, and degrades, with no host at all.
IAddon for the Chroma vector database backend.
On initialize! it configures the Chroma connection, builds a
ChromaMemoryStore, connects it and registers it in the hive-spi memory
registry: under `:registry-key` (default `:chroma`), and as the ACTIVE
store only when no other backend holds that slot (an addon never evicts
another backend; `:active? true` in the config forces it, which is what a
deployment whose `:services :memory-store :backend` is chroma wants).
It also offers Chroma as the host's IVectorCollectionStore, again only
when none is installed yet (hive-chroma.host/install-vector-store!).
Config (manifest :addon/config, overridden by the init config):
:host :port :collection-name the Chroma endpoint (defaults
CHROMA_HOST / CHROMA_PORT env, then
localhost:8000, hive-mcp-memory)
:registry-key registry slot, default :chroma
:active? claim the :default slot even when taken
:vector-store? offer the vector-collection port, default true
No namespace here requires the host: everything host-side goes through
hive-chroma.host, i.e. through hive-spi's host-services registry, so this
loads, and degrades, with no host at all.What initialize! reads; every key optional.
What initialize! reads; every key optional.
(create-addon)(create-addon _config)A ChromaAddon. The optional config is applied at initialize!.
A ChromaAddon. The optional config is applied at initialize!.
(resolve-config cfg)(resolve-config cfg env-fn)Pure over ENV-FN: the effective connection + registration config. Explicit config wins, then CHROMA_HOST / CHROMA_PORT, then defaults.
Pure over ENV-FN: the effective connection + registration config. Explicit config wins, then CHROMA_HOST / CHROMA_PORT, then defaults.
cljdoc builds & hosts documentation for Clojure/Script libraries
| Ctrl+k | Jump to recent docs |
| ← | Move to previous article |
| → | Move to next article |
| Ctrl+/ | Jump to the search field |