Repository navigation
docs: show a Recall investigation on the homepage and across the docs - #1171
Merged
Merged
Conversation
kvlonge
enabled auto-merge (squash)
October 20, 2026 00:07
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.
Why
Recall shipped in 0.161.0 and 0.162.0, but the homepage, README and docs home did not mention it, the docs never showed it answering a question, and nothing said when to use Recall rather than sinks or the execution history API. The roadmap and feature comparison still listed ClickHouse as a future adapter.
Changes
sqb recall outputshows what the build printed, and--backend warehousefinds the bad row and its cause. Real output from the example project, run on 0.162.0.sqb recallin the command table, ClickHouse and SQLite in the adapter list.Verification
scripts/check_links.py: 0 broken links.