Opened 2 weeks ago
Closed 2 weeks ago
#35421 closed New feature (wontfix)
Add support for ParadeDB's pg_search bm25 index in Django
| Reported by: | Philippe Noël | Owned by: | |
|---|---|---|---|
| Component: | contrib.postgres | Version: | |
| Severity: | Normal | Keywords: | postgres search fts |
| Cc: | Philippe Noël | Triage Stage: | Unreviewed |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
Hi everyone,
I'm one of the makers of ParadeDB. We create the Postgres extension pg_search (formerly known as pg_bm25), which adds Elasticsearch-level full-text search to Postgres. You can read more here: https://github.com/paradedb/paradedb/tree/dev/pg_search
We've seen asked on the Django forums (see here: https://forum.djangoproject.com/t/elasticsearch-quality-inside-postgresql-paradedb-introduces-pg-bm25/24654) for support by Django for the pg_search BM25 index.
I'm not familiar with Django deeply-enough to know where to start, but we'd love to partner up and build this feature together. Let us know!
Note:
See TracTickets
for help on using tickets.
Thank you for your report.
I don't think that Django can commit to providing abstractions for all Postgres extensions out there, the good news though is that it provides a tons of entry points for custom fields, migration operations, indices, and lookups to be created.
I'd suggest you look into maintaining your own third-party applications that provides the adequate abstraction to leverage your commercial offering. That's what vendors like Cockroachdb and other extensions maintainer do.