-
Notifications
You must be signed in to change notification settings - Fork 70
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
Determine options to switch search engine #761
Comments
We should also mention Solr is not well supported by our current (Haystack based) toolset. Supported backends are listed here. The toolset "seems" to support Solr 7.x now. However we're using an older version of the tools with Solr 8.11.2. Solr version 9.x is the current major release with plans for 10.x. All versions of Solr <8.11 are EOL. The tools seem to have always been one version behind on their support. |
Since we've gotten the unbound queries somewhat under control (by blocking them), performance has been fantastic. We still have to find a search engine with better support. |
From ZenHub issue: See bcgov/orgbook-configurations#137 for background information. Possible options:
Acceptance Criteria:
|
Performance continues to be fantastic since we've blocked the unbound queries through expression filtering. |
So just close this issue and we can search for this if needed? |
I think we still want to look at other options, since the support for Solr, at least with the tech stack we're using, is not great. The fact that things are working makes this far less urgent though. |
I know that BC Registries is using Solr elsewhere, and it is really their project, their call. Enterprise Apps is not going to be making such a change, or spending time on this. |
So we leave it here and open for them. |
I've taken it off our board. |
Our Solr implementation is performing poorly due to difficulty in optimizing the search indexes as well as not being well-suited to live in OpenShift. We should determine a viable option for a new search engine that we could switch the project to.
The text was updated successfully, but these errors were encountered: