search for: nerdl

Hi all, I upgraded from Ferret 0.11.3 to Ferret 0.11.4 because I was getting intermittent segfaults that seemed to be due to a bug which was fixed (changeset 749). Unfortunately, 0.11.4 + acts_as_ferret seems to be a bad combination. I''m getting the some "fs_store/File Not Found Error occured at <except.c>:117" which was reported in the "Constant 0.11.4

I''ve been running some multithreaded tests on Ferret. Using a single Ferret::Index::Index inside a DRb server, it definitely behaves for me as if all readers are locked out of the index when writing is going on in that index, not just optimization -- at least when segment merging happens, which is when the writes take the longest and you can therefore least afford to lock out all reads.

Hi all, I''m using fuzzy~ queries which can return very poor matches. What is the most elegant way to filter out scores below some threshold? I know that I can do my own thing with find_id_by_contents but I''d like to filter out less relevant results at a lower level so that I can use :limit/:offset for pagination and all that. What am I missing? Thanks, Casey