Repository navigation
[docs](lance) Document automatic vector and BM25 SQL search - #4441
Merged
Merged
Conversation
Gabriel39
had a problem deploying
to
Production
October 22, 2026 06:23 — with 
GitHub Actions
Failure
GitHub Actions
Failure
Gabriel39
had a problem deploying
to
Production
October 22, 2026 10:54 — with
GitHub Actions
Failure
GitHub Actions
Failure
Gabriel39
had a problem deploying
to
Production
October 22, 2026 23:23 — with
GitHub Actions
Failure
GitHub Actions
Failure
6 of 11 tasks
morningman
added a commit
that referenced
this pull request
Oct 23, 2026
## Summary The Russian planner keeps reopening four deletion tasks from its fixed T03 inventory after the Binlog-to-Changelog renames in #4426. Record the reviewed deletions so subsequent plans stop requesting cleanup that is already complete. The ledger binds each task to its original ID, source path and source hash, with a timestamp, explicit machine-review identity and evidence from #4426/#4431. At Apache master `a0312e41f13f47ff7da7855759d0d6f7ed3b5fc1`, all four replacement Russian documents are current, obsolete sources/targets/state records are absent, affected inbound links and sidebars are clean, and the actual Docusaurus `createRedirects` callback maps all four old Russian URLs to their replacements. The remaining references to the old image filename point to an existing retained asset. ## Validation - Existing planner tests: 19 passed, including reviewed-deletion suppression and evidence validation. - Configuration checks pass for all three managed locales; the four ledger records pass `validateResolved`. - Native audit and planner comparison: deletion tasks drop from 4 to 0. Coverage and all six unrelated source-update tasks remain unchanged: required/current/pending = 3354/3348/6; no sidebar gaps or planner exceptions. - Shared Russian PR preflight and `git diff --check` pass. No document bodies or page-state records change, so preflight checks zero changed documents. - All four Russian redirect mappings verified through the loaded Docusaurus configuration. No website build or public deployment was performed locally; CI selects Russian 4.x. The six remaining Russian 4.x tasks come from the later source changes in #4441: four new distance-function documents and updates to Lance Catalog and hybrid search. This ledger change preserves those tasks and does not claim complete current coverage. ## Self-review | Checkpoint | Conclusion | | --- | --- | | Goal | Four completed historical cleanup tasks disappear from planning while new source work remains visible. | | Scope and clarity | One locale-specific ledger file; original inventory and translation identities are preserved. | | Information architecture | Current docs, active versions, community pages and other locales retain their existing content and navigation. | | Paths, links and redirects | No paths or anchors change here; all four existing replacement routes, cleanup and redirects were checked. | | Frontend and build conventions | No frontend, style, theme, workflow or build changes. Responsive/theme behavior is unaffected. | | Verification | Native audit/planner comparison, existing planner tests, configuration/schema validation, actual redirect callback and shared admission checks cover the metadata change. CI/public deployment results are not asserted. | | Other correctness, accessibility, SEO and maintenance | No additional issue found in this change. Ledger evidence and machine identity remain explicit; six new source-update tasks are reported separately. | ## Versions - [x] dev - [x] 4.x - [ ] 3.x - [ ] 2.1 or older (not covered by version/language sync gate) ## Languages - [ ] Chinese - [ ] English - [x] Russian translation-state ledger ## Docs Checklist - [x] Checked by AI - [ ] Test Cases Built (metadata-only change; existing tests and native checks run, no new tests or website build) - [x] Updated required version and language counterparts, or explained why not - [x] If only one language changed, confirmed whether source/translation counterparts need sync The ledger belongs only to Russian. The existing English/Chinese sources, Russian replacement documents and shared redirects are already merged and need no counterpart edits for this bookkeeping change. Co-authored-by: morningman <moringman@apache.org>
This branch was previously deployed
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.
Ordinary SQL search over Lance is not described in the current 4.x reference. This documents the branch-4.2 behavior introduced by apache/doris#69346 (implementation PR is still open; this documentation depends on it).
For example, an eligible
ORDER BY cosine_similarity_approximate(embedding, [0.1,0.2,0.3,0.4]) DESC LIMIT 10becomes native Lance cosine retrieval, with1 - _distanceprojected as similarity. Exact functions and ACL/EXISTS queries retain scalar distance evaluation and global Top-N.cosine_distance_approximate,cosine_similarity_approximate,hamming_distance, andhamming_distance_approximate, including normal, zero/empty, NULL, and out-of-range examples.Version scope: this change intentionally updates 4.x English and Chinese only. The implementation targets
branch-4.2, not Doris master; current/development and older-version pages are not being advertised as supporting it. This explains the governance version-counterpart warnings. Availability wording requires a Doris 4.2 build containing this capability, rather than implying every build with the explicit TVFs already supports rewriting.Validation: all 12 changed documentation pages compiled with the Docusaurus MDX processor; changed-page link checks found no broken links; SQL-function structure checks passed; paired English/Chinese SQL blocks match; all six added sidebar references resolve; whitespace and added-content disclosure checks passed. SEO descriptions satisfy the configured length range. Remaining SEO duplicate-title warnings reflect shared SQL identifiers across locales and existing versioned titles. Full-repository sidebar lint reports unrelated existing findings. Full site build and live SQL execution were not run.