IShutdownHook for the Proximum Datahike-backed temporal store. Priority 215 — runs after pure client closers (qdrant/chroma at 210) because Proximum syncs its konserve backing store to disk before releasing the Datahike connection, and may share a classloader path with other datahike-backed stores that need to settle first.
Binds IShutdownHook and the lifecycle registry from hive-spi, so there is
no compile-time coupling to hive-mcp at all. The memory ports are reached
by runtime resolve, matching hive-proximum.init.
Sync+close sequence:
disconnect! (flushes konserve under the hood).Each step is independently guarded; a failure in one does not skip
the next. The outer try catches Throwable so the orchestrator's
priority walk continues on error.
IShutdownHook for the Proximum Datahike-backed temporal store.
Priority 215 — runs after pure client closers (qdrant/chroma at 210)
because Proximum syncs its konserve backing store to disk before
releasing the Datahike connection, and may share a classloader path
with other datahike-backed stores that need to settle first.
Binds IShutdownHook and the lifecycle registry from hive-spi, so there is
no compile-time coupling to hive-mcp at all. The memory ports are reached
by runtime resolve, matching `hive-proximum.init`.
Sync+close sequence:
1. (hive-proximum.state/get-handle) — snapshot backend handle
2. Release Datahike connection via the store's protocol
`disconnect!` (flushes konserve under the hood).
3. (hive-proximum.state/clear-handle!) — atom bookkeeping.
Each step is independently guarded; a failure in one does not skip
the next. The outer `try` catches Throwable so the orchestrator's
priority walk continues on error.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 |