PARITY.md: link kNN fallback to tracking issue MobilityDB#840#93
Closed
estebanzimanyi wants to merge 1 commit intodoc/parityfrom
Closed
PARITY.md: link kNN fallback to tracking issue MobilityDB#840#93estebanzimanyi wants to merge 1 commit intodoc/parityfrom
estebanzimanyi wants to merge 1 commit intodoc/parityfrom
Conversation
The R-tree kNN fallback (seq-scan + sort + limit) is now formally
tracked in MobilityDB#840, which lays out the four-stage plan:
1. Box-to-box minimum-distance primitive in MEOS
2. Priority-queue R-tree traversal
3. Public RTreeNNCursor API
4. MobilityDuck consumes the API to replace the fallback
The PARITY.md paragraph now points readers at the tracking issue so
future visitors can follow progress and decision points instead of
just seeing a description of the gap.
Also tightened the prose: removed "currently" (the gap is the
present state, not a recent regression) and expanded the contractions
("doesn't" → "does not", "isn't" → "is not") to match the surrounding
formal documentation style.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This was referenced May 1, 2026
Member
Author
|
Superseded by the consolidated PR branch |
1 task
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
1 participant
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.
Summary
Updates the kNN paragraph in `doc/PARITY.md` to point at the new tracking issue `MobilityDB#840`, which lays out the four-stage plan to add an `RTreeNNCursor` API to MEOS and replace the seq-scan fallback in MobilityDuck once the API lands.
What changed
```diff
The kNN operator `|=|` works syntactically (`ORDER BY col |=| q LIMIT k`
-gives correct results), but currently falls back to seq-scan + sort +
-limit because MEOS' R-tree doesn't yet expose a priority-queue scan.
-Output is correct; throughput on large tables isn't.
+gives correct results), but falls back to seq-scan + sort + limit
+because MEOS' R-tree does not yet expose a priority-queue scan.
+Output is correct; throughput on large tables is not. Tracked in
+MobilityDB#840,
+which lays out the four-stage plan to add a `RTreeNNCursor` API to
+MEOS and replace the fallback in MobilityDuck once the API lands.
```
Why
Future visitors of `PARITY.md` can follow progress and decision points on the gap rather than just reading a description of it. The tracking issue carries the API design, sequencing relative to PR #740 (SP-GiST), and the five decision points for @mschoema and @nhungoc1508 to settle.
Editorial tweaks made in passing
🤖 Generated with Claude Code