similar to: Away for a week

Hi Everyone, I''m using Ferret 0.10.11 with acts_as_ferret from SVN (same results with 0.10.10 and 0.10.9 though). I''m running into an odd problem where the scores of my top-ranking search results are ridiculously small - even when the query is one that should match at least one document with a decent score. To give an example, I have just the names of 5 businesses indexed

Hey folks, A lot of confusion has been caused by having stop-words filtered by the default analyzer. There have been a few suggestions to remove this feature so I thought I''d put it to a vote. Making this change would not be backwards compatible and would require users to either rebuild their indexes or change their code to keep the same stop-words settings. However, it would save a lot

Hi there, What''s the current status of the Windows port? I may be in a position to lend a hand over the next couple of weeks - where should I start looking? And what''s the best way to get SVN HEAD? This happens: $ svn checkout svn://www.davebalmain.com/ferret/trunk ferret svn: Can''t connect to host ''www.davebalmain.com'': Connection refused --

Hi German users, Can one of you guys give me a German Phrase that I can use to demonstrate tokenizing non-ascii text. Preferably something about 40 bytes long with lots of umlauts and perhaps a ?. Cheers, Dave

Hi All, Hope all is going well. Was just wondering if anyone has implemented a grep style output page of hits using Ferret as the index/query engine? Any thoughts about how best to implement it? The previous thread discussess highlighting - would that be the best approach to follow or is there a better way? Cheers, Marcus -- Posted via http://www.ruby-forum.com/.

Hey guys, Now that the Lucy[1] project has Apache approval and is about to begin, the onus is no longer on Ferret to strive for Lucene compatability. (We''ll be doing that in Lucy). So I''m starting to think about ways to improve Ferret''s API. The first part that needs to be improved is the Document API. It''s annoying having to type all the attributes to

Hi all, Having problems trying to get Ferret to read an index generated by Lucene. Am I right in thinking Ferret should be able to read a Lucene generated index no problem? Using the code snippets detailed in http://www.ruby-forum.com/topic/64099#new Any advice gratefully received. Many Thanks, Steven -- Posted via http://www.ruby-forum.com/.

Hey all, I''m back. Some of you are probably thinking that is the longest weeks vacation on record. Well, I''d like to take this opportunity to apologise for my absence and offer a brief explanation. When I got back to Australia I naturally went home to visit my parents, only to find that they have been hit really hard by the drought. They didn''t really tell me just how

Hey, Luke doesn''t seem to be able to open a Ferret index I''ve created. Is this expected? If yes, can someone recommend another index inspection tool? Thanks, John

Hi, I''m currently trying to set up a solution involving multiple servers using the same index over nfs. The problem is that from what I have seen, ferret doesn''t support multiple processes writing to the same index. Using a DRb service is not an option since this would create a single point of failure. I tried using Ferret::Store::FSDirectory to create a write lock on the the

Hi List, I''ve took some time and made some tests on the performance of java-lucene, hyperestraier and ferret as Dave encourages the community of ferret to do so. Quite intersting numbers. Ferret indeed deserves to be called a high-performance port!! It''s MyFirstBenchmark ( http://ferret.davebalmain.com/trac/wiki/MyFirstBenchmark ) so please don''t be too cruel on

Hi, >From looking at Ruby sources it seems that every update method deletes and reinserts documents. It makes sense if indexed fields are changed but what if it is not the case? It would speed up update a lot indexes did not have to be updated twice for nothing. Any quick way to do it? -- Sergei Serdyuk Red Leaf Software LLC web: http://redleafsoft.com -- Posted via

Hi, We''re using Ferret 0.9.4 and we''ve observed the following behavior. Searching for ''fieldname: foo and bar'' works fine while ''fieldname: "foo and bar"'' doesn''t return any results. Is there a way to make ferret recognize the ''and'' inside the query as a search term and not an operator? (I hope I got the

Izit Izit wrote: > Correction on my previous post. > > The correct way to do it is: > > Product.find_by_contents("*",{},:conditions =>search_conditions,:include > => [:supplier],:order =>"products.id" ) > > Leave out the :limit=>:all that is put in by default. Exactly - I tried to make aaf a bit more clever by letting it assume :limit

I''m getting some results that I don''t understand from a search. The code, based on the tutorial, and the results are below. Everything makes sense to me, except the results for the ''title:"Some"'' query. I would think that it should match the first two documents, but not the third. What am I missing here? Thanks for any help! --- code

Hey guys, I''ve just removed the -fno-stack-protector flag from the release so those who had trouble because of this should now be able to install 0.11.2-rc3. If you have any problems with this release, please let me ASAP. Cheers, Dave -- Dave Balmain http://www.davebalmain.com/

Remember folks, we can support the Ferret project by donating warm soft electronic cash to the author, Dave Balmain, using the paypal buttons on the website: http://ferret.davebalmain.com/trac http://ferret.davebalmain.com/trac/wiki/DonationsFAQ We can also buy the Ferret Shortcut pdf/book from O''Reilly, also written by Dave Balmain. It''s awesome good:

godspeed, steve. thanks for giving us the tools to catch fish. -bowerbird -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://six.pairlist.net/pipermail/markdown-discuss/attachments/20111006/3e1c11bd/attachment.htm>

Hi Folks, I''ve just released version 0.9.0. This latest version of Ferret is an alpha release. I have removed the old c extension and Ferret is now running on a fully ported C library. This has allowed some huge performance improvements both with regard to memory and CPU usage. There will probably be a few portability issues to start with. It has been developed on Linux so it should

Hey guys, Just released Ferret 0.11.1. Hopefully this will fix *most* of the problems people were having. Now that I know gcc hides stack overflows on Ubuntu because -fstack-protector is set, I won''t get caught by that one again. Anyone know any other gotchas I should be aware of on Ubuntu. Please try the new version and let me know if you are still having problems with it. I have until