Eliminate staged search

Bug #1698206 reported by Mike Rylander on 2017-06-15
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

We've tried in the past to move from our current search mechanism, which trades completeness of results for performance, to a pure-SQL, completely accurate search. It didn't work out then, but, hope springing eternal, a new attempt was made. The forthcoming branch implements the output of a research project funded by MassLNC over the course of the last year or so. The result is:

 * Faster core search, esp. for searches that are not over-broad
 * Faster page rendering, esp. for search results, though across the board to some degree
 * Fully accurate search results, including in the face of consortial configurations where, previously, small library's items could be omitted from result sets
 * Reliance on and, more positively, access to new Postgres features

Mike Rylander (mrylander) wrote :

Branch pushed at http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/miker/lp-1698206-eliminate_staged_search ... The baseline schema has /not/ been synced to the upgrade script, so testing will require running that after installation. I'm putting that off until any bugs are worked out of the DB-level code.

Mike Rylander (mrylander) wrote :

And, finally, the commit message should make for a good release notes entry.

tags: added: pullrequest
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers