Search doesn't find some exact text matches in description
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
New
|
Undecided
|
Unassigned | ||
Bug Description
When we converted the epics-base bug database for import into Launchpad, we added the original bug ID to the description text in the form mantis-<n> in the assumption that this would make it easy to find those bugs on Launchpad. However this doesn't actually work; for example an advanced search for "mantis-334" or "mantis 334" at https:/
Luckily we also named our bugs so I know that I can get to it by editing the URL to
https:/
but we shouldn't have had to explain that to all our users.
The problem is not the presence of numbers since "line 344" does return a result and other searches do work. Interestingly a search for "mantis-302" finds only our bug mantis-331, whose description text actually contains the string "mantis 302" (with a space instead of the hyphen) and I suspect this implies that your whole-text-indexer is using a different definition of a word than your search engine. Maybe the indexer takes "mantis-302" as a single word, but the search engine is splitting words at hyphens before looking them up?
| Andrew Johnson (anj) wrote | #1 |
Can I stress this, I think it's important in tracking down the problem: A search for "mantis-302" finds a bug that contains "mantis 302" but not the bug that contains "mantis-302".