similar to: Large File Support? (FAQs are broken)

Hi, I''m trying to figure out how to compile ferret with large file support, but none of the topics that discuss this actually say How this is done. Can someone please provide the info? thanks. -m my exact problem: http://www.ruby-forum.com/topic/94143#191630 this topic also discusses the issue: http://www.ruby-forum.com/topic/84237#151791 this topic says that the FAQ should have the

I need to reset the ferret index between test runs. It seems like there are a few ways to reset the ferret index. * Deleting the index directory -- is this really bad form? * calling rebuild_index * (any others?) What would y''all recommend? (Sorry, I''m from Texas) Preferably, I''d like a way to reset the index that I can integrate into a selenium test. -David

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''m getting an exception when I query a large index (4GB, ~700K docs) on a particular field. For example: supplier_id:77490 IO Error occured at <except.c>:93 in xraise (IOError) Error occured in fs_store.c:293 - fsi_seek_i seeking pos -1515676213: <Invalid argument> Anecdotally it seems to happen for supplier_ids > 76900. Here is the field info for that

Hello list, As there is still some large file support bugs in the 0.11.4 release I had to download the trunk and apply a patch sent in by kyle http:// ferret.davebalmain.com/trac/ticket/215. The problem is now that the highlighting doesn''t work. Somehow it combines excerpt_length with num_excerpts so if you have and excerpt_length of 50 and num_excerpts of 5 and you get only one

Hello, I''m using Ferret trunk (#770) with Kyle''s large file support patch: http://ferret.davebalmain.com/trac/ticket/215 I''m having trouble with Ferret::Search::Searcher#highlight returning too much text around the query term. Regardless of what I set :excerpt_length to, highlight returns the entire contents of the field up to the first occurrence of the search

I was optimizing a 650MB using ferret (0.11.3) and I received the following error. I''ve seen some people have similar issues but I haven''t seen any resolutions. The contents of the index directory follow the error. Has anyone seen anything like this and found a resolution? Many thanks. /mnt/apps/search/releases/20070622175637/script/../config/../vendor/

Hello everyone, We need to create backups of our index, but there are a few constraints: - our application shouldn''t go offline for that - it has to be done quickly Ferret doesn''t seem to have this kind of functionnality (though I''m very new to Ferret, I may be wrong), and I figured that I couldn''t do it using plain Ruby (it''s way too slow, try with

I am using Ferret for a Rails app in which Rails runs as one user but I have other processes that run as a different user that modify the ferret index. This is done in large part to mitigate the damage if a major exploit is found in Rails again. The problem is Ferret creates all its index files with rw for the user only. I have included a small patch that changes Ferret to create these

Hi, I keep getting locking errors when updating my index which puzzles me since only one process is supposed to be accessing the index at a time (at least in development mode). I''m using Ferret with Rails (NOT acts_as_ferret, though) and employed an observer to add a new document to the index when a new ActiveRecord is created. I''m not sure if this has any impact on the

We are using Ferret on our site answeru.com. Today all of a sudden we started getting Ferret errors while users were trying to register or log into the system. I am not a Ferret techie - I apologize if a similar problem has already been asked or if it is not really a Ferret issue. Any ideas: IO Error occured at <except.c>:79 in xraise Error occured in fs_store.c:324 - fs_open_input

Hi, I''m adding some news articles to a keyed Ferret 0.10.14 index and encountering quite serious instability when concurrently reading and writing to the index, even though with just 1 writer and 1 reader process. If I recreate the index without a key, concurrent reading and writing seem to work fine (and indexing is about 10 times quicker :) I''m testing by running my indexing

During our last week of Ferret / aaf usage (also our first week of Ferret / aaf usage), I have received 8 messages stating that our app encountered a Ferret::QueryParser::QueryParseException. For instance: A Ferret::QueryParser::QueryParseException occurred in foo#search: Error occurred in src/q_parser.y:279 - yyerror couldn''t parse query "com -- 404". Error message

Hi, I use ruby console to experiment acts_as_ferret, but I ran into file rename error when I try to rebuild index after doing a search. is this normal? I am using Ferret 0.10.9 in windows XP. Loading development environment. >> Address.rebuild_index => {} >> Address.find_by_contents(''US'') => #<ActsAsFerret::SearchResults:0x4f2ffcc @total_hits=2,

Hi, I noticed a 0.11.3 release and gave it a whirl. I''ve so far not been able to reproduce any segfaults with my ferret_killer[1] script, though I do get some errors. when the searching process is running and I start the indexing process, I immediately get: /usr/lib/ruby/gems/1.8/gems/ferret-0.11.3/lib/ferret/index.rb:692:in `latest?'': File Not Found Error occured at

We''ve been running Ferret for a few months on our site with great result. But, just a monent ago the index suddenly became corrupt. It all started with this error message: :108250 is out of range [0..108183] for IndexWriter#[] /usr/local/lib/ruby/gems/1.8/gems/ferret-0.10.9/lib/ferret/index.rb:382:in `[]'' And after that every search resulted in this error: A IOError

For my weekend project, I''m going to get form_remote_tag and file_column playing happily together. According to my research, no one has done this yet. If you happen to have tried this, and have some workable code, send me an email. I''d rather not duplicate the effort. Thanks! -- Kyle Maxwell Chief Technologist E Factor Media // FN Interactive kyle@efactormedia.com

hi, i''m indexing a really large db table (~4.2 million rows). i''ve noticed that after ~2M records, index performance decreases by almost an order of magnitude. full dataset graph here: http://i122.photobucket.com/albums/o244/spokeo/indexer-data.jpg here''s a couple best-fit lines that represent the data points: 0-2M : y = 78.65655x + 144237.5 2.5M+ : y = 10.79832x +

Thanks for the update. Are you updating nouveau for GK208 and GM206? Regards, On Tue, Feb 23, 2016 at 4:11 PM, Kyle McMartin <kyle at infradead.org> wrote: > On Tue, Feb 23, 2016 at 06:55:59PM +0900, Alexandre Courbot wrote: > > Hi linux-firmware maintainers, > > > > The following changes since commit > f66eccaab7d605d433cb82e389441b21ec99b40f: > > > >

I have a large index (~6GB, ~1 million docs) that was built by RDig. I wrote a script to iterate through the index to clear out some duplicate information to try to reduce the size of the index. clients.each {|client| docs = RDig.searcher.search("+supplier_id:#{client.id}") docs.each {|doc| data = doc[:data].dup #the contents of the web page new_results = {}