feat(supabase): add SupabaseGroongaDocumentStore and SupabaseGroongaRetriever

[ShubhamGond105]

Related Issues

• fixes SupabaseGroongaDocumentStore and SupabaseGroongaRetriever #3083

Proposed Changes:

Adds SupabaseGroongaDocumentStore and SupabaseGroongaRetriever for full-text search powered by PGroonga, a PostgreSQL extension for fast multilingual full-text search exposed by Supabase.

• SupabaseGroongaDocumentStore: stores and searches documents using PGroonga full-text search — no embeddings needed
• SupabaseGroongaRetriever: retrieves documents using plain text queries
• Follows the same structure as the merged PR feat: Add Supabase integration with PgVector document store and embedding retriever  #3164 (SupabasePgvectorDocumentStore)
• Can be used alongside SupabasePgvectorEmbeddingRetriever in hybrid search pipelines

How test

19 unit tests covering:

• Default and custom init parameters
• write_documents, delete_documents, filter_documents, count_documents
• Serialization round-trip (to_dict / from_dict)
• Retriever init, run, and serialization
• Empty query handling
• DuplicatePolicy (OVERWRITE, SKIP, FAIL) handling

Notes for the reviewer

• Followed the same structure as PR feat: Add Supabase integration with PgVector document store and embedding retriever  #3164 as a blueprint
• Used supabase-py client for all database operations
• PGroonga must be enabled on the Supabase project as a prerequisite
• Happy to make any adjustments based on feedback

Checklist

• I have read the contributors guidelines and the code of conduct
• I have updated the related issue with new insights and changes
• I added unit tests and updated the docstrings
• I've used one of the conventional commit types for my PR title: feat:

[ShubhamGond105]

Hi @davidsbatista,
I'm actively working on fixing the remaining CI issues:

count argument type error — need to use CountMethod.exact instead of "exact" string
result.data union-attr error in _groonga_retrieval — need stronger type guard
Will push fixes shortly.
Happy to get any other feedback in the meantime!

[davidsbatista]

Can you confirm that the client doesn't support async operations? You did not add any do the SupabaseGroongaDocumentStore

[davidsbatista]

Can you also define an async def run_async(...) ? Does the client supports it?

[davidsbatista]

Hi @ShubhamGond105 - do you still have time to work on this?

[ShubhamGond105]

Yes but I need more time to fix it.

[davidsbatista]

@ShubhamGond105 thanks for your contribution. I've tackled the remaining issues: filters, integration tests, CI/CD, etc.