similar to: How did ferret sort by the column?

I may have run across a bug in Ferret: if throws a segmentation fault when I try to create a Sort object using the default fields (SCORE and DOC_ID), but setting reverse to true. Here''s the minimal example: #!/usr/bin/env ruby require ''rubygems'' require ''ferret'' Ferret::Search::Sort.new Ferret::Search::Sort.new( [

I have the acts_as_ferret plugin installed. Everything searches great, but I would like to limit the results (i.e. by ''end_date'') and sort them (by ''end_date''). ''end_date'' is a valid column in my "posts" table. Here''s the code I have already: @posts = Post.find_by_contents(params[:query]) params[:query] comes from a

Ferret throws a bus error in the unit tests under Solaris, sun4u architecture. http://ferret.davebalmain.com/trac/ticket/272 Bug reporter appears to be on Solaris 8 with Ruby 1.8.4. I''ve tried on Solaris 10 (first release and 10/06, first without and then with the most recent patch set), both with Ruby 1.8.6, and get exactly the same error in the same spot. Tried with 0.11.4 and also

I have the acts_as_ferret plugin installed. Everything searches great, but I would like to limit the results (i.e. by ''end_date'') and sort them (by ''end_date''). ''end_date'' is a valid column in my "posts" table. Here''s the code I have already: @posts = Post.find_by_contents(params[:query]) params[:query] comes from a form. I

I found it quite fun to generate index by ferret. However, I had to use lucene now. Can I use the index that I''ve already done by ferret? ps. Lucene 2.2.0 vs Ferret 0.11.4 Thx! -- Posted via http://www.ruby-forum.com/.

hi all! after hours of trying to find contents with german umlauts i stumbled upon a post where someone said ferret won''t work with utf-8 on windows??? is that really true? do i really have to iconv everything to iso-8859-15 before indexing and do the same with the query to get it working? i''m running ruby 1.8.5, ferret 0.10.9-mswin32, and rails 1.2.2 and just reinstalled aaf

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

I am a bit puzzled. I am having issues with memory leaking away. It seems to be related to searching documents by ''id'' column value. This is what I am doing: cached_annotations = Ferret::Index::Index.new(:path => "#{RAILS_ROOT}/db/ferret/tmp/annotations", :auto_flush => false) 100000.times { |x| doc=cached_annotations[x.to_s] } Every 100000.times eats 100MB

Hello list, I just started using ferret and it really doesn''t go my way. Doing gem install ferret outputs -> make install /usr/bin/install -c -m 0755 ferret_ext.so /var/lib/gems/1.8/gems/ ferret-0.10.13/lib make clean Successfully installed ferret-0.10.13 Installing ri documentation for ferret-0.10.13... Installing RDoc documentation for ferret-0.10.13... In ferret.rb ->

Dave and all, I run a medium RoR app using Ferret and acts_as_ferret. I get a lot of lock errors. Not always but around 5% of all searches (aspecially during peak periods). Here are the messages I get: A NameError occurred in szukaj#index: uninitialized constant Ferret::Index::Index::LockError [RAILS_ROOT]/vendor/rails/activesupport/lib/active_support/dependencies.rb:478:in

Using the current ferret gem (on Win-XP): irb(main):001:0> require ''ferret'' c:/ruby/lib/ruby/1.8/fileutils.rb:950: warning: already initialized constant OPT_TABLE => true irb(main):002:0> include Ferret => Object irb(main):003:0> index = Index::Index.new => #<Ferret::Index::Index:0x3477ba8 @qp=nil, ...> irb(main):004:0> index << "This is

QueryParser fails badly allocating enormous amount of memory when processing query strings with special/accented characters. See: irb(main):002:0> require ''rubygems'' irb(main):003:0> require ''ferret'' irb(main):004:0> include Ferret irb(main):005:0> index = Index::Index.new irb(main):008:0> index << "something" # Now the error

Greetings. Apologies if I missed something like this in the archives or internet, but I''m having issues using Ferret with Rails. Specifically, I have a class class "Weight" in my application (it happens to be a model). My app runs perfectly fine until it first executes "require ''ferret''". At that point, my definition of the class "Weight"

Hi guys! Been reading this list for a while. I have two repeatable Ferret crash bugs, both seg faults. 1. The first bug appears to seg fault Ferret when you use quotes in a search argument (eg ''file_name:"file name"'') 2. The second bug appears to seg fault Ferret when you attempt to index text with very long tokens (above 256 chars). It may have something to do with

Hello. I''m trying to use the ''acts_as_ferret'' gem with Rails. Rails: 1.1.4 and 1.2.3 OS: WinXP I''ve installed both Ferret and the plugin using Ruby Gems: C:\>gem install ferret Successfully installed ferret-0.11.4-mswin32 Installing ri documentation for ferret-0.11.4-mswin32... Installing RDoc documentation for ferret-0.11.4-mswin32... C:\>gem install

Up to now in my ferret development I have been using simple single-word strings as my search queries. I just now am trying to increase the complexity of my queries. When I was passing a single word with no spaces in my index searches, like so: count = index.search_each(''testing'') do |d, s| ... end everything worked fine. But now when I do something like this: count =

I am using Locomotive 2.0.8 with Rails 1.2.3 for development. It works great. I recently installed Ferret 0.11.4 as a gem. The installation seemed to go fine. No error or warning messages. I setup a test rails app to try Ferret, and the server won''t start. The error I get is /Applications/Locomotive2/Bundles/rmagickRailsJan2007_x86.locobundle/

Thanks for the response Jens. Indeed I am sorting by something other than relevancy, so that would explain it. Optimized, it''s extremely fast and handles a good load, but new records kill it until I optimize. I haven''t tried :merge_factor as I wasn''t aware of it. I''m not sure it will help given the above. Regarding the re-index locking code,

Hi, following the discussion about acts_as_ferret on the Rails mailinglist, there was an issue about transactions, which could result in beind the database and ferret out of sync. I have taken a different approach from acts_as_ferret trying to resolve the transaction problem. Instead of adding things to the ferret index in the model, I have added it in the controller. I have only the create part

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