Skip to content

docs: adding Supabase to docs#11488

Open
davidsbatista wants to merge 13 commits into
mainfrom
doc/adding-Supabase
Open

docs: adding Supabase to docs#11488
davidsbatista wants to merge 13 commits into
mainfrom
doc/adding-Supabase

Conversation

@davidsbatista
Copy link
Copy Markdown
Contributor

Proposed Changes:

  • Adding Documentation for the Supabase Document Store

Checklist

  • I have read the contributors guidelines and the code of conduct.
  • I have updated the related issue with new insights and changes.
  • I have added unit tests and updated the docstrings.
  • I've used one of the conventional commit types for my PR title: fix:, feat:, build:, chore:, ci:, docs:, style:, refactor:, perf:, test: and added ! in case the PR includes breaking changes.
  • I have documented my code.
  • I have added a release note file, following the contributors guidelines.
  • I have run pre-commit hooks and fixed any issue.

@davidsbatista davidsbatista requested a review from a team as a code owner June 2, 2026 12:36
@davidsbatista davidsbatista requested review from bogdankostic and removed request for a team June 2, 2026 12:36
@vercel
Copy link
Copy Markdown

vercel Bot commented Jun 2, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
haystack-docs Ready Ready Preview, Comment Jun 3, 2026 3:17pm

Request Review

@claude
Copy link
Copy Markdown

claude Bot commented Jun 2, 2026

Code review

No issues found. Checked for bugs and CLAUDE.md compliance.

@claude
Copy link
Copy Markdown

claude Bot commented Jun 2, 2026

Code review

No issues found. Checked for bugs and CLAUDE.md compliance.

@bogdankostic bogdankostic changed the title adding Supabase to docs docs: adding Supabase to docs Jun 3, 2026
Copy link
Copy Markdown
Contributor

@bogdankostic bogdankostic left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The SupabaseDocumentStore page looks good in general.

The changes made to the API reference should be made by adapting the docstrings. Also, it would be good to add pages for the retrievers and copy the content to the latest versioned docs.

Comment thread docs-website/reference/integrations-api/supabase.md
Comment thread docs-website/docs/document-stores/supabasedocumentstore.mdx Outdated
@davidsbatista
Copy link
Copy Markdown
Contributor Author

I will add the retrievers in a different PR

@davidsbatista
Copy link
Copy Markdown
Contributor Author

I will add the retrievers in a different PR

Actually, maybe better to add them as well with this PR

The reference file is auto-generated by CI. Remove branch-local
modifications so the PR does not alter it.
@davidsbatista
Copy link
Copy Markdown
Contributor Author

Removed the auto-generated file from the PR

Copy link
Copy Markdown
Contributor

@bogdankostic bogdankostic left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looking good, just two minor comments.

Let's copy the pages also to the v2.30 docs before merging.


Unlike embedding-based retrievers, this Retriever works with plain text queries and requires no embeddings. It supports a wide range of languages out of the box through PGroonga's multilingual indexing capabilities.

The Retriever can be combined with `SupabasePgvectorEmbeddingRetriever` and a [`DocumentJoiner`](../joiners/documentjoiner.mdx) for hybrid search pipelines that take advantage of both keyword and semantic retrieval.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

DocumentJoiner is technically not needed anymore thanks to our smart pipeline connections (but it's not wrong either to use it).


- [Oracle](../../document-stores/oracledocumentstore.mdx)
- [Pgvector](../../document-stores/pgvectordocumentstore.mdx)
- [Supabase](../../document-stores/supabasedocumentstore.mdx) — managed PostgreSQL with pgvector (vector search) and PGroonga (multilingual full-text search)
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For all other document stores we have no description, for consistency I wouldn't add it here either.

Suggested change
- [Supabase](../../document-stores/supabasedocumentstore.mdx) — managed PostgreSQL with pgvector (vector search) and PGroonga (multilingual full-text search)
- [Supabase](../../document-stores/supabasedocumentstore.mdx)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants