Repository navigation
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
Conversation
…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.
… k3d leaves the kubeconfig of the machine alone
ambergrove
approved these changes
Nov 14, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
spec.distributed.frontend.allowReset, false by default.
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 warning of the passage to Chroma says now, as the README since #25:
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.