Repository navigation
|
I use self-hosted Hindsight and need to add a reviewed set of documents to an existing populated bank while normal Retain and consolidation remain enabled. The import must either commit as one durable unit against a reviewed source/target state, or reject without a partial import if a relevant dependency changes. An unrelated concurrent retain should neither be lost nor silently treated as part of the reviewed import. The v1.2.0 transfer documentation describes
I saw Discussion #1876 about restoring a fresh bank with source writes paused. My question is specifically about merging into a populated bank while ordinary writes continue. I would appreciate a pointer to the closest supported contract or existing issue. |
Replies: 2 comments
|
Short answer: no — as of the v1.2.0 transfer docs, there is no supported conditional, all-or-nothing merge into an existing bank while Retain keeps running, and no bank-revision precondition is documented. What exists is 1. No fence / atomicity. 2. Distinguishing rejected / partial / committed. The import returns 3. The recommended safe boundary is what you guessed: pause the writers — or avoid merging into the live bank at all. The pattern the docs do support is the blue-green one from #1876: import into a fresh bank (restore refuses an existing target, by design), verify it, then point clients at the new bank. That gives you the atomicity you want at the cost of a cutover, instead of a merge. If a cutover isn't possible and the import must land in the live bank, pausing Retain (and auto-consolidation, which the import itself triggers like a retain) for the duration of the import is the safe boundary. I would not plan a conditional-import feature on the roadmap from this thread — that's a maintainer decision — but the docs as written don't offer one. One caveat: I haven't run this merge path myself — the above is from the current transfer/import documentation, not from a test on your instance. If the maintainers have added a revision precondition since v1.2.0, they'd be the ones to point at it. |
|
Hi @djallits — following up on my answer above from 2026-11-12 (no supported conditional, all-or-nothing merge into a live bank while Retain keeps running; |
Short answer: no — as of the v1.2.0 transfer docs, there is no supported conditional, all-or-nothing merge into an existing bank while Retain keeps running, and no bank-revision precondition is documented. What exists is
mode=merge, and it is weaker than what you're asking for in exactly the ways you suspected:1. No fence / atomicity.
POST …/transfer/import?mode=merge&document_conflict=skip|replace|new-idruns as a background operation and works at document granularity: a conflicting document is skipped, replaced, or given a new id, per the policy you pick. It does not dedupe facts, so re-importing the same archive can leave overlapping observations over the same facts, and there is no d…