Repository navigation
Conversation
Rework the Lakebase Search landing page to lead with search built for agents instead of a list of search types. Add the problem framing (scaling vector search in Postgres past pgvector), an architecture section with a diagram, a "what you get" section, a qualitative benchmarks pointer to the Databricks engineering blog, and a demoted search-types reference. Keep pgvector first-class: lakebase_vector is positioned as a pgvector-compatible superset. Co-authored-by: Isaac <no-reply@databricks.com>
|
@bgrenon is attempting to deploy a commit to the neondatabase Team on Vercel. A member of the Team first needs to authorize it. |
Expand HNSW on first use, describe Jev as a reranking model on Neon AI Gateway, and reword the what-you-get opener to the pgvector-compatible path to scale rather than a pgvector alternative. Co-authored-by: Isaac <no-reply@databricks.com>
Lead the opener with the developer payoff, write to "you", add natural contractions, drop an idiom and a corporate attribution phrasing, and make a couple of abstractions concrete. No facts, structure, or guardrails changed. Co-authored-by: Isaac <no-reply@databricks.com>
Collaborator
Author
|
Superseded by #6782, which is the same change as a normal same-repo branch (this one was accidentally opened from a fork, so Vercel preview and the SDK check could not run). |
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.
What this changes
Rewrites the Lakebase Search hub page (
content/docs/ai/lakebase-search.md) into an architecture-first, developer-facing overview.Previously the page opened with a list of search types. It now leads with how Lakebase Search works and why it scales, which better matches how developers and AI coding tools look for this information.
New structure:
pgvector stays first-class throughout.
lakebase_vectoris positioned as a pgvector-compatible superset (same types, operators, and SQL), not a replacement.Notes for reviewers
Pending confirmation before this leaves draft
This pull request and its description were written by Isaac.