search for: kinosearch

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 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 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 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 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, 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

Early[0] implementations of Swish3 for Perl are now available on CPAN. http://search.cpan.org/dist/SWISH-Prog-KSx/ http://search.cpan.org/dist/SWISH-Prog-Xapian/ These Perl implementations offer KinoSearch[1] or Xapian[2] as alternate backend libraries. SWISH::Prog::Xapian should build indexes compatible with the swish_xapian tool that comes with libswish3. Feedback welcome. [0] They are "early" because libswish3 1.0 has not yet been released. [1] http://search.cpan.org/dist/KinoSearch-...

Does anyone have experience with linux tools to parse the text from common non-text file formats for searching? I'm trying to use the kinosearch add-on for twiki which is fine as far as the search goes, but it takes forever to generate the index. It uses xpdf to extract strings from pdf's, antiword for .doc, and since it is perl, the Spreadsheet::ParseExcel module for .xls. Some documents parse/index quickly, some extremely slowly,...

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

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

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/.

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

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