Skip to content

Frontend allowReset, the passage from Chroma 1.5.9 to VecturaDB 1.0.0-preview.9, and SPANN in the warning of the passage to Chroma - #26

Merged
Laurianti merged 6 commits into
mainfrom
frontend-allow-reset
Nov 14, 2026
Merged

Laurianti merged 6 commits into
mainfrom
frontend-allow-reset

Conversation

@Laurianti

@Laurianti Laurianti commented Nov 14, 2026 •

Copy link
Copy Markdown
Member

spec.distributed.frontend.allowReset, false by default.

  • With true, the operator sets CHROMA_ALLOW_RESET on the frontend, as the values.dev.yaml of Chroma's chart does for Chroma's tests.
  • Anyone who reaches the frontend can then delete all the data with reset.
  • The condition ResetAllowed shows it: True with reason AllowReset, False with reason ResetRefused.
  • The field is only on the frontend, which serves reset.
  • The chart reference has a new case, reset, rendered by build/chart.sh with the otherEnvConfig of values.dev.yaml.

The passage from Chroma 1.5.9 to VecturaDB 1.0.0-preview.9, the latest release: its row in the table, after its trial.

  • The trial, on AKS: an Azure disk opened by Chroma 1.5.9 with 200 dense records, then by VecturaDB 1.0.0-preview.9.
  • The dense records are intact, with the same ids and results. The three records at distance 0 of the query come in the order of their ids, where Chroma 1.5.9 gives another order.
  • BM25 and sparse vectors were written and searched. Two runs, with the same outcome.
  • The releases of VecturaDB before 1.0.0-preview.9 have no row to it: their passage is refused with UpgradeNotKnown.
  • With 0.1.3, data written by 1.0.0-preview.9 and then opened by Chroma 1.5.9 with allow-product-change could not go back to VecturaDB: 1.0.0-preview.9 had no row from Chroma 1.5.9, and 1.0.0-preview.5 is a downgrade from it. Measured on AKS with 0.1.3: ProductChangeNotKnown.
  • With the row the data can go back: the unit test LatestToChromaForcedAndBack covers it, and in the trial preview.9 read its data intact after Chroma 1.5.9.

The warning of the passage to Chroma says now, as the README since #25:

  • Chroma 1.5.9 cannot read a SPANN collection: count, get and query fail with Collection is missing HNSW configuration, and an add answers an error yet writes the record.
  • It links the section "Going back to Chroma 1.5.9" of VecturaDB's migration guide. The page it pointed to no longer has the advice.
  • Measured on AKS with 0.1.3, on data written by 1.0.0-preview.9.

The image on .NET 10.0.15, the security update of 10 November: the two base images pinned at their 10.0.15 digests, the SDK 10.0.404 and the chiseled ASP.NET Core runtime 10.0.15. They replace #22 and #23, which still bring 10.0.14.

A new k3d cluster, in build/e2e.sh and in the README, gets --kubeconfig-update-default=false too: with --kubeconfig-switch-context=false alone, k3d still writes the cluster into the kubeconfig of the machine.

The release notes of 0.1.4, in build/release-notes.md.

Tests: each change of the operator has unit tests that fail without it. The end-to-end tests pass on k3d with the image on .NET 10.0.15.

…d accept reset

false by default, as before. true sets CHROMA_ALLOW_RESET on the frontend, between CONFIG_PATH and RUST_BACKTRACE, as
values.dev.yaml of the chart does for the tests of Chroma: anyone who reaches the frontend can then delete all the data.
The condition ResetAllowed says which: True with the reason AllowReset, False with ResetRefused. The field is only on the
frontend, which serves reset. The case reset of build/chart.sh renders the chart with the otherEnvConfig of values.dev.yaml,
and ChartTests compares the objects with it.
… SPANN collection

The message of the status, as the README since #25: Chroma reads the records, documents and metadata of the HNSW
collections; a SPANN collection it lists, but count, get and query fail with Collection is missing HNSW configuration, and
an add answers an error yet writes the record. VecturaDB reads every collection again once it opens the data. The link goes
to Going back to Chroma 1.5.9 of the guide, as the page it pointed to no longer has the advice.
…st release

Its row in Passages.Known, after its trial: on AKS, an Azure disk opened by Chroma 1.5.9 with 200 dense records, then by
VecturaDB 1.0.0-preview.9: the dense records intact, with the same ids and results, the three records at distance 0 of the
query in the order of their ids; BM25 and sparse vectors written and searched; two runs with the same outcome. The releases
of VecturaDB before it have no row to it.

With operator 0.1.3, data that VecturaDB 1.0.0-preview.9 wrote, opened by Chroma 1.5.9 with allow-product-change, could not
go back to VecturaDB: 1.0.0-preview.9 had no row from Chroma 1.5.9, and 1.0.0-preview.5 is a downgrade from it. The row lets
it go back.

1.0.0-preview.9 is the latest release in the tests, in the examples and in the README.
@Laurianti
Laurianti requested a review from a team as a code owner November 14, 2026 21:01
@Laurianti
Laurianti merged commit 254c9a2 into main Nov 14, 2026
4 checks passed
@Laurianti
Laurianti deleted the frontend-allow-reset branch November 16, 2026 18:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants