Opened 7 years ago

Last modified 6 years ago

#4817 new defect

Journal partial matching not working

Reported by: Eben Owned by: marco
Priority: high Milestone: Future Release
Component: sugar-datastore Version:
Keywords: Cc:
Blocked By: Blocking:
Deployments affected: Action Needed:
Verified: no

Description

http://dev.laptop.org/ticket/2423 claims to have added partial matching to the Journal, but I can't seem to get it to function. The following is pasted from a message on the sugar list:

Hey everyone,

I'm just giving two B4s with build 624 a spin around the block and have
noticed an odd issue with the search in the journal.

Let's assume I have this file called
"QSVU07_Bsp2_ChristophDerndorfer_0425826.pdf" stored on a USB thumbdrive
that's accessable via the journal. If I do a search for "qsvu" the file
turns up nicely. However if I search for "Bsp2", "*Bsp2", "Bsp2*" or
"*Bsp2*" the file isn't displayed. Same thing holds true if I look for
"Christoph", "*Christoph", "Christoph*" or "*Christoph*". Only files
whose name start with "Christoph..." are displayed.

On the other hand I also have a file called "OLPC Text Test.txt" on that
thumbdrive and search for "text" or "test" does immediatly turn up the
file I was looking for.

So my question is: Am I missing something here about the syntax of the
search or is this a bug?

Change History (8)

comment:1 Changed 7 years ago by jg

  • Milestone changed from Never Assigned to Update.1

comment:2 Changed 7 years ago by marco

  • Owner changed from tomeu to marco

comment:3 Changed 7 years ago by marco

  • Component changed from journal-activity to datastore
  • Keywords update.2? removed
  • Milestone changed from Update.1 to Retriage, Please!

blah* is supported, *blah* is not supported. I doubt there is anything we can do about this for Update.1. This is what the datastore currently support (and probably what xapian support).

comment:4 Changed 7 years ago by Eben

I'm of the opinion that typing "blah" should implicitly perform a search for "*blah*". That's the real problem. If in the time being we only support one wildcard in a given word, then "blah" should be interpreted as "*blah blah*" for now.

comment:5 Changed 7 years ago by marco

The problem is that the datastore can't perform *blah* at all.
blah* is already implicit.

comment:6 Changed 7 years ago by Eben

That's why I suggest searching for *blah and (technically or) blah* and show results for both, for now.

comment:7 Changed 7 years ago by kimquirk

  • Milestone changed from Retriage, Please! to Update.2

comment:8 Changed 6 years ago by marco

  • Milestone changed from Update.2 to Future Release
Note: See TracTickets for help on using tickets.