Open gbp opened 3 years ago
does not support all of Xapian’s features (such as spelling correction, synonyms or replication)
Guess we should close this given the above?
Still worth considering if this would speed up running the test suite as these features aren't always necessary on the test environment.
Xapian Ruby bindings can create in-memory search indexes and these should be faster for our current approach of writing test index to disk and restoring before each spec.
The xapian_db gem has this feature but doesn't it yet supports the Xapian 1.4.x which we use. I have tested and gem's tests pass when using
xapian-full-alaveteli
bindings instead of the 1.2.x ones provided an older version ofxapian-ruby
.It might be worth seeing if we could swap out our legacy acts_as_xapian gem as part of this invesigation.