search for: multiread

Hey.. i am just browsing through the lucene features and i''m wondering if this feature is available in ferret as well .. # multiple-index searching with merged results this would be nice, as i''m thinking about several indexes, as i am using a lot of wildcard queries for livesearches like google suggest. i think the performance would increase, if i split my rather big index in

...d method `get_field_names'' for #<Ferret::Index::IndexReader:0x406059dc> and even if I could, I cant pass any fields to the QueryParser qp.fields = ["title"] NoMethodError: undefined method `fields='' for #<Ferret::QueryParser:0x407db070> So I tried using the MultiReader, like acts_as_ferret does, but it won''t take any arguments @reader = Index::MultiReader.new(sub_readers) ArgumentError: wrong number of arguments (1 for 0) Is everything I''m trying to do unimplemented in the c version, or am I just overlooking something obvious? thanks, joshua...

Hi, I have an index where each document contains an untokenized ''url'' field. I would like to query the index for the most popular urls. In SQL I would do this via a Group By clause. Is there anything in Ferret that will do something similar? I found this discussion that proposed a solution involving TermEnums:

...use-case might be to have multiple indexes to speed up indexing. If for example you are scraping websites it is a very good idea to have multiple scraping processes. The best way to do this is to have each process indexing to its own index. You could then search all indexes at once using a MultiReader or you could also merge all indexes into a single index." Does anyone have any recommendations as to whether one method is superior to the other? We have a system where we build multiple indexes from scraping websites and need to expose the indexes as a web application--the web app...

Hi there, Sorry if this has come up before, but I couldn''t see it obviously addressed anywhere. There are a few methods in IndexReader that raise NotImplementedErrors. I''m specifically interested in get_term_vector, but there are a number of others. Is there anything specific holding these back, or would patches to implement them be accepted? Thanks, -- Alex

...runs every 10 minutes or so. I''m guessing that the best approach is to create an IndexWriter for each update run, which can be closed and discarded at the end of the update run. Or can I close and reuse a single IndexWriter? I searched http://ferret.davebalmain.com/api for details on the MultiReader, but I couldn''t find any details. If someone could post a link to point me in the right direction that would be great. Thanks so much Neville

...nored. Furthermore, reading several indexes should be done like that: index = Ferret::Index::Index.new( :path => [ ''/some/path'',''/another/path'' ], :readonly => true ) so you dont need to play around with MultiSearcher or MultiReader Classes. And if possible (and if this api isn''t downward compatible anyway) i would suggest to drop one ''Index'' in Ferret::Index::Index We have a Ferret::Document, a Ferret::Field, so why not have a Ferret::Index .. doesn''t make sense to have a Ferret::Index:...

i''m using Ferret 0.9.0 with acts_as_ferret (the one from svn.jkraemer.net), and i''m getting duplicate results, as described in this thread: http://rubyforge.org/pipermail/ferret-talk/2005-December/000048.html is there a way to configure the indexes created by acts_as_ferret to use :key => :id, as described in that thread? i''ve poked around in the code, and had

I have been trying to use multi_search to search accross multiple associated models, but I have had no luck at all. I have scoured the net and this forum for all similar posts, but none of them contain enough code for me to get it to work. I am successfully able to search individual models, and then display the results without a problem. I have the following 2 models, Product and Component.