#201 closed enhancement (fixed)
NEAR search with two OR subqueries should be supported
| Reported by: | Richard Boulton | Owned by: | Olly Betts |
|---|---|---|---|
| Priority: | normal | Milestone: | 1.0.12 |
| Component: | Library API | Version: | SVN trunk |
| Severity: | normal | Keywords: | |
| Cc: | Blocked By: | ||
| Blocking: | Operating System: | All |
Description (last modified by )
In trunk this now throws UnimplementedError, but it really should be supported:
import xapian
a=xapian.Query('A')
b=xapian.Query('B')
c=xapian.Query(xapian.Query.OP_OR, a, b)
d=xapian.Query(xapian.Query.OP_NEAR, c, c)
Change History (9)
comment:1 by , 17 years ago
| Blocking: | 120 added |
|---|
comment:2 by , 17 years ago
| Owner: | changed from to |
|---|
Oh, I have a partially written patch for this somewhere...
comment:3 by , 17 years ago
| Operating System: | → All |
|---|---|
| Status: | new → assigned |
comment:5 by , 16 years ago
| Description: | modified (diff) |
|---|---|
| Milestone: | → 1.1 |
comment:6 by , 16 years ago
| Blocking: | 120 removed |
|---|
(In #120) Remove the unfixed dependencies so we can close this bug - they're all marked for the 1.1.0 milestone.
comment:7 by , 15 years ago
| Description: | modified (diff) |
|---|
Fix formatting of description.
We should at least fix the AssertionError here, and that should be easy to do so let's try to do it for 1.0.0.
I did work on a patch to implement NEAR and PHRASE over subqueries but I didn't fully finish it and I'm not sure where it is now.
comment:8 by , 15 years ago
| Description: | modified (diff) |
|---|---|
| Milestone: | 1.1.0 → 1.1.1 |
| Summary: | Attempting to create a NEAR search with two OR nodes gives assertion error → NEAR search with two OR subqueries should be supported |
| Type: | defect → enhancement |
comment:9 by , 15 years ago
| Milestone: | 1.1.1 → 1.0.12 |
|---|
Fixed in trunk r12228.
Setting milestone:1.0.12
comment:10 by , 15 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Fixed for 1.0.12 in branches/1.0 r12258.
Note:
See TracTickets
for help on using tickets.
Marking as for 1.0.x - would be nice to fix soon, but certainly shouldn't block a release.