Re: case-sensitivity in searches?
Hi dBera, --On Monday, February 16, 2009 09:25:44 PM -0500 D Bera dbera@gmail.com wrote: As you figured out this has to do with the Locate backend. You can run beagle-query with argument source:Files to only search the filesystem backend. I wonder why the filesystem backend did not return results from your home directory. After restarting beagled (and waiting a bit), there's now results with source:Files as well. There is a possibility that something criticial crashed on the beagled side - which is preventing the filesystem backend from responding - which could cause both the above behaviours. You can send SIGUSR1 to beagled to turn on its debug output (oh wait ... ubuntu probably disables the debugging at build time - you can try to run beagled with --debug to see if you get any useful information). When I disable the Locate backend, beagle-query exits after ~19s; otherwise it takes ages, even when I use source:Files. But (slightly OT) I'm wondering why the following query $ /usr/bin/time beagle-query source:Files filename:reconnaissance --verbose gives this debugging output Debug: Parsed query 'source:Files' as prop query:key=beagle:Source, value=Files and property type=Keyword Debug: Parsed query 'filename:reconnaissance' as OR of 2 queries: Debug: :key=beagle:NoPunctFilename, value=reconnaissance and property type=Text Debug: :key=beagle:SplitFilename, value=reconnaissance and property type=Text Error: LocateDriver can only search for text and does not support 'OR', 'NOT' queries. I thought that the operator AND would be used implicitly - and not OR as mentioned in the quotation (in the wiki it says To indicate that the word A or word B be in results, use OR). But perhaps only the debugging output is wrong on this one. Furthermore I don't understand the error from the LocateDriver, since I explicitly searched in the Files backend. There are no results from Locate, but I'm wondering whether the other backends are searched as well, but only filtered from the result list? Oh, and I'm subscribed to dashboard-hackers, so I receive answers to the list :) Thanks and greetings, Jens ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
case-sensitivity in searches?
Hi everyone, while I'm at it, I happen to have another question, this time concerning the case of search terms. It seems that the search is case-sensitive, and I was wondering whether Lucene allows for case-insensitive lookups, or whether there is already a (undocumented) modifier I can use. Thanks and greetings, Jens pgpAxezM5Zscq.pgp Description: PGP signature ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: problems with beagle-build-index after upgrade to 0.3.8
Hi dBera, --On Monday, February 16, 2009 07:24:28 AM -0500 D Bera dbera@gmail.com wrote: Nothing I can remember that would cause this. Could you use lsof to figure out what kind of files are left opened for a long time ? lsof should show about 10/20 indexable/data files that are opened at any time and they should disappear after 5/10 seconds at the most. After running beagle-build-index on the heavy data set for a while, the number of open files kept growing; I killed the process at 257 open files, copied all those files to another directory, and re-ran beagle-build-index on them. The result was the same - shortly before finishing (no ulimits broken) the number of open files was at ~266. It's mostly .chm files, so maybe there's something broken? The (small) index is fine, btw. The output of beagle-build-index is mostly Debug: +file://... ... Debug: -file://... with some errors here and there, but no obvious signs of problems with the .chm files. Anything else I can do to debug further? Greetings, Jens pgpsN0T8zdILB.pgp Description: PGP signature ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: case-sensitivity in searches?
Hi dBera, --On Monday, February 16, 2009 07:26:07 AM -0500 D Bera dbera@gmail.com wrote: Search is not (supposed to be) case-sensitive. Can you double check ? Sure, I did a simple search on a filename: $ /usr/bin/time beagle-query Reconnaissance --verbose Returned latest 4 results out of total 4 matches Uri: file:///home/user/Reconnaissance.z8 PaUri: (null) Snip: (null) Type: File MimeT: beagle/x-locate-result Src: Locate Score: 1 Time: 2007-08-05 14:10:39 (Utc) beagle:ExactFilename = 'Reconnaissance.z8' beagle:Filename = 'Reconnaissance' beagle:FilenameExtension = '.z8' beagle:FileType = 'document' beagle:HitType = 'File' beagle:MimeType = 'beagle/x-locate-result' beagle:NoPunctFilename = 'Reconnaissance' beagle:Source = 'Locate' beagle:SplitFilename = 'Reconnaissance' (...) Elapsed time: 1.182s Total hits: 4 Command terminated by signal 2 0.84user 0.03system 6:55.50elapsed 0%CPU (0avgtext+0avgdata 0maxresident)k 0inputs+200outputs (0major+4595minor)pagefaults 0swaps but the following search did not return any results: $ /usr/bin/time beagle-query --stats-only reconnaissance Elapsed time: 0.706s Command terminated by signal 2 0.75user 0.04system 1:25.00elapsed 0%CPU (0avgtext+0avgdata 0maxresident)k 0inputs+16outputs (0major+4479minor)pagefaults 0swaps On a sidenote I am wondering whether beagle-query would eventually exit (by itself - as you can see, I killed both instances) Greetings, Jens ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
