feat!: rename bm25 APIs to paradedb and always use the paradedb access method - #13
Open
rebasedming wants to merge 1 commit into
Open
feat!: rename bm25 APIs to paradedb and always use the paradedb access method#13rebasedming wants to merge 1 commit into
rebasedming wants to merge 1 commit into
Conversation
rebasedming
requested review from
isaacvando,
mdashti,
philippemnoel and
stuhood
as code owners
July 27, 2026 15:25
rebasedming
changed the title
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.
What
Implements paradedb/paradedb#5706 as a breaking rename — no configurability, no fallbacks:
renderBm25IndexDdl/Bm25IndexDdlOptions/Bm25VectorIndexColumn→renderParadeDbIndexDdl/ParadeDbIndexDdlOptions/ParadeDbVectorIndexColumn(old names removed)'bm25'contract index type is removed;'paradedb'is the only index type and DDL always emitsUSING paradedbpg_amprobing anywhere; the demo contract usestype: 'paradedb'Requires pg_search 0.25.0+.
Tests
Package: 43/43, typecheck + build clean. Demo end-to-end against a pg_search 0.25.0 dev server: db:init creates the index
USING paradedb(verified in pg_catalog), all CLI commands pass, 6/6 integration tests with zero skips. Released images fail at db:init as expected.