Opened 14 years ago
Closed 13 years ago
#418 closed enhancement (fixed)
wildcard search in omega
| Reported by: | Do | Owned by: | Olly Betts |
|---|---|---|---|
| Priority: | normal | Milestone: | 1.2.5 |
| Component: | Omega | Version: | 1.0.17 |
| Severity: | normal | Keywords: | |
| Cc: | Blocked By: | ||
| Blocking: | Operating System: | All |
Description
It seems Omega doesn't support wildcard search. So I feature request to add it.
ps. Or it is unusable/not effective to be used? As I understand wildcarded word searched not by prefix, but first searched in (other) database by prefix, then query expanded to 23456 words which are ORed and searched again in main database. (This to my ignorant non-IR-scientific view looks strange. Why not just search by prefix in the first place?)
Change History (2)
comment:1 by , 14 years ago
| Milestone: | → 1.2.x |
|---|
comment:2 by , 13 years ago
| Milestone: | 1.2.x → 1.2.5 |
|---|---|
| Resolution: | → fixed |
| Status: | new → closed |
Implemented in r15323 - now any QueryParser flags can be set from omegascript.
Note:
See TracTickets
for help on using tickets.
Omega really needs a generic way to set (or clear) QueryParser flags. We can cleanly add that in 1.2.x without breaking compatibility, so setting the milestone.
We can't "just search by prefix" as we don't have an index which tells us all the documents which match a given term prefix. So we have to merge the posting lists for all the terms that the wildcard expands to.
It is possible to keep an index for term prefixes to accelerate wildcard expansions (see #207), but that will take significantly more space. For most users that probably isn't worthwhile so it's likely to be an index-time choice.