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

Use PostgreSQL for full text search #720

Open
Tracked by #771
sunu opened this issue May 2, 2023 · 2 comments
Open
Tracked by #771

Use PostgreSQL for full text search #720

sunu opened this issue May 2, 2023 · 2 comments

Comments

@sunu
Copy link
Collaborator

sunu commented May 2, 2023

PostgreSQL's full text search capabilities should be good enough to handle our need for basic full text search and filtering.

Additionally, we will be able show search results from all documents a user has access to compared to the current state where we show search results from published documents only. (See #759) Although it is possible to implement document level access control in ElasticSearch through filtering, it's much easier to implement through PostgreSQL.

Switching to PostgreSQL will allow us to drop our dependency on OpenSearch/ElasticSearch and simplify our stack as a result.

@bwbaker1
Copy link
Collaborator

@wrynearson Is this necessary? I don't see the need for users to search for all of their documents. Is the bigger issue a need to drop OpenSearch/ElasticSearch?

@sunu
Copy link
Collaborator Author

sunu commented Jul 13, 2023

@bwbaker1 I think this is mostly a nice to have and not something we need to do. It also depends on whether we think #759 is an issue worth fixing or not.

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