Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Replace Java-based search engine with Postgresql full-text search #1035

Open
mvl22 opened this issue Aug 8, 2022 · 2 comments
Open

Replace Java-based search engine with Postgresql full-text search #1035

mvl22 opened this issue Aug 8, 2022 · 2 comments

Comments

@mvl22
Copy link
Member

mvl22 commented Aug 8, 2022

Agreed to investigate this in due course following the redesign.

Useful article:
https://tanzu.vmware.com/content/blog/pg-search-how-i-learned-to-stop-worrying-and-love-postgresql-full-text-search

@wookey
Copy link

wookey commented Oct 17, 2024

There is also xapian full-text search which is fast and versatile. I've only used it via Omega which just indexes the whole site by traversing the URLs, but you can connect it direct as a ruby-gem: https://github.com/gernotkogler/xapian_db, which would allow incremental update.
I don't know how that compares with using the postgres built-in text search, in terms of pros and cons, but I thought it worth bringing to your attention.

@mvl22
Copy link
Member Author

mvl22 commented Oct 17, 2024

which just indexes the whole site by traversing the URLs

The search has to have full permissions capability though. For instance, committee members need to be able to search for things that only they should be able to see.

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

No branches or pull requests

2 participants