case-sensitivity in searches?

[Jens Dönhoff-2]

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

_______________________________________________
Dashboard-hackers mailing list
Dashboard-hackers@...
http://mail.gnome.org/mailman/listinfo/dashboard-hackers

[D Bera]

Hi Jens,

> 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

Search is not (supposed to be) case-sensitive. Can you double check ?

- dBera

--
-----------------------------------------------------
Debajyoti Bera @ http://dtecht.blogspot.com
beagle / KDE fan
Mandriva / Inspiron-1100 user
_______________________________________________
Dashboard-hackers mailing list
Dashboard-hackers@...
http://mail.gnome.org/mailman/listinfo/dashboard-hackers

[Jens Dönhoff-2]

Hi dBera,

--On Monday, February 16, 2009 07:26:07 AM -0500 D Bera
<dbera.web@...> 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@...
http://mail.gnome.org/mailman/listinfo/dashboard-hackers

[Jens Dönhoff-2]

Hi again,

--On Monday, February 16, 2009 04:14:29 PM +0100 Jens Dönhoff
<mailinglists@...> wrote:

>   Src: Locate

It seems that the Locate backend is causing the case sensitivity
problems.

Thanks anyway :)

Greetings,

Jens
_______________________________________________
Dashboard-hackers mailing list
Dashboard-hackers@...
http://mail.gnome.org/mailman/listinfo/dashboard-hackers

[D Bera]

> 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
...
> MimeT: beagle/x-locate-result
>  Src: Locate

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.

> On a sidenote I am wondering whether beagle-query would eventually exit (by
> itself - as you can see, I killed both instances)

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

- dBera

--
-----------------------------------------------------
Debajyoti Bera @ http://dtecht.blogspot.com
beagle / KDE fan
Mandriva / Inspiron-1100 user
_______________________________________________
Dashboard-hackers mailing list
Dashboard-hackers@...
http://mail.gnome.org/mailman/listinfo/dashboard-hackers

[Jens Dönhoff-2]

Hi dBera,

--On Monday, February 16, 2009 09:25:44 PM -0500 D Bera
<dbera.web@...> 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@...
http://mail.gnome.org/mailman/listinfo/dashboard-hackers

[D Bera]

> When I disable the Locate backend, beagle-query exits after ~19s; otherwise
> it takes ages, even when I use source:Files.

Hmm... I will remember to check up on this.

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

filename:abc becomes an OR query - either the fullname is abc or abc
is one of the words in the fullname (or something like this ... think
of filenames with underscores, spaces etc.).

You are right otherwise, your query becomes "source:files AND filename:..."

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

No ... the Locate driver or other drivers are not searched at all if
source:xxx is explicitly mentioned. But the query first needs to be
sent to all the backends for technical reasons, and it is then you see
this error output. It is normal behaviour.

I don't fully remember, but if Locate and Files backend return the
same results (i.e. both return results from your home dir), then there
might be some problem.

- dBera

--
-----------------------------------------------------
Debajyoti Bera @ http://dtecht.blogspot.com
beagle / KDE fan
Mandriva / Inspiron-1100 user
_______________________________________________
Dashboard-hackers mailing list
Dashboard-hackers@...
http://mail.gnome.org/mailman/listinfo/dashboard-hackers